bug: Telemetry Invalid Context JSON
See original GitHub issueI’m seeing 3 events this morning that are causing failures in the Snowflake staging of the telemetry data because theres invalid json in the contexts column. I was able to narrow it down to this snippet of the contexts field. It almost looks like the user ran something like meltano invoke dbt-snowflake:run\
with the backslash in their plugin command, and we just passed it through. So it ends up acting as an escape character for the context json thats generated.
{
"schema": "iglu:com.snowplowanalytics.snowplow/contexts/jsonschema/1-0-1",
"data": [
{
"schema": "iglu:com.meltano/plugins_context/jsonschema/1-0-0",
"data": {
"context_uuid": "c03c812e-d912-4996-aad8-ee6367f6de90",
"plugins": [
{
"category": "transformers",
"name_hash": "5ce17935e3051fb03c316f7a01e66fad78c8f3d799c12673f39d5cece817df26",
"namespace_hash": "33e3de565605b33042aa3ff5953cfba66bc7c5212d8caf0775acb9523fcb84da",
"executable_hash": "de371adefe4de7fe43b17dd1d87d8d47eab2f506eb5dfed54560638e894018f7",
"variant_name_hash": "c39e17256a61578d1c3bb160f9c73ae64f81e9f9541f9874670e840c6d9db66d",
"pip_url_hash": "96a16e0c3fff2ed8facc9a4d89a5364a8704afcd8a853d53a67e9ab60606ab45",
"parent_name_hash": "5ce17935e3051fb03c316f7a01e66fad78c8f3d799c12673f39d5cece817df26",
"command": "run\"
}
]
}
}
I’m not sure exactly if this is a meltano bug, a bug with snowplow (allowing invalid json through), or something I should handle in Snowflake. I could definitely handle it in Snowflake but I would expect that our pipeline of schema validation wouldnt allow invalid json to get through so wanted to flag it.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top GitHub Comments
@WillDaSilva I appreciate you looking into this. I agree that its safe to ignore it for now if we can’t reproduce it. It was only a single event in our entire data set so who knows what happened. I’ll keep you posted if I see it again.
@WillDaSilva I’m also not able to re-produce it locally but I did notice that it was on Windows so maybe that has something to do with it. Here the full context object I get with the message. This is also from Snowflake. Snowplow/Snowcat Cloud drops the data into our S3 bucket as TSV files, then we COPY it into Snowflake, I cant see how that would make a difference but wanted to put it all on the table.