We have a storage loader failing with an unwanted json schema pulled from the snowplow assets .
This did not happen earlier and its now become very frequent.
s3://snowplow-hosted-assets-us-east-1/4-storage/redshift-storage/jsonpaths/org.w3/performance_timing_1.json
Any idea how to fix this ?
ihor
2
@psundaramoorthy7508, if you do not need data related to performance_timing
you can disable it in your tracker initialization code
contexts: {
performanceTiming: false, // <-- this triggers performance_timing if set to true
}
The relevant data is loaded into org_w3_performance_timing_1
table.
I think you may just need to add the table to your database for the load to complete successfully.
Not the most elegant solution though.