A partner recently asked us:
We are passing mobile_context in iOS, shouldn’t we have networkType and networkTechnology in schema 1-0-1? Currently its not even a column in the table. Schema in the table does say 1-0-1.
The updated Redshift table definition and JSON Paths files for
mobile_context version 1-0-1 are being “held back” in the Blocked schemas milestone currently. That milestone contains various other contexts and events which are lagging the latest schema published in Iglu Central.
These migrations are being held back because releasing them would break existing Snowplow installations. If we upgrade the JSON Paths file in
s3://snowplow-hosted-assets to contain all the 1-0-1 fields, then this upgraded version will conflict at load time with the existing tables deployed in users’ Redshift databases. Snowplow users’ pipelines will fail to load Redshift due to no fault of their own.
This is due to an architectural mistake we introduced with our original shredding technology. The medium term fix is to implement the full table migration capabilities that we are working towards in Iglu and Snowplow. In the short-term there is an easy workaround:
- Deploy the 1-0-1 table version into your Redshift database
- Add the 1-0-1 JSON Paths file into your own
jsonpath_assets:S3 bucket at the appropriate path
Because of the way that the StorageLoader works, your local copy of the 1-0-1 JSON Paths file will take priority over the centrally hosted 1-0-0 version in