Remove wheel and passive event listener feature flags
See original GitHub issueWe have an existing batch pipeline that uses the latest JavaScript Tracker along with R87 components for Enrich and Storage.
All events recorded using 2.9.1 are now going into bad rows with the following error:
{
"errors": [
{
"level": "error",
"message": "error: object instance has properties which are not allowed by the schema: [\"f_passive\",\"f_wheel\"]\n level: \"error\"\n schema: {\"loadingURI\":\"#\",\"pointer\":\"/items\"}\n instance: {\"pointer\":\"/0\"}\n domain: \"validation\"\n keyword: \"additionalProperties\"\n unwanted: [\"f_passive\",\"f_wheel\"]\n"
}
],
}
f_passive
and f_wheel
seems to have been introduced by the following commit: https://github.com/snowplow/snowplow-javascript-tracker/commit/a28888111dc8ea66ca8339396bd00a2f84c4d5db#diff-3e7c17598500b655533daae15e659338R275
It is unclear what other environmental factors are necessary for the issue to appear so I am listing everything that might be relevant:
- Enrichment runs on R87
- Tracker is configured to POST to the collector
- At least one other vendor uses Snowplow on the pages where we are integrated into
- Static Iglu repositories are used for resolution (iglucentral.com and one private)
I have not yet been able to find the JSON schema that the “web” portion of the events are validated against and I am now investigating upgrade paths. It would be helpful if someone could point me to where the validation occurs so I can identify the earliest version the issue would be fixed with.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top GitHub Comments
I’ve got the patch done, should be able to get this out today.
The new release is mirrored now.