Here are the sections after the fold:
This release defines the following new tables for Redshift:
To successfully shred the Tracker’s new event and context JSONs into the new Redshift table definitions, we have defined new JSON Paths files:
In support of this, we released a new version of the
link_click JSON Schema to Iglu Central, with SchemaVer 1-0-1 (compare link_click 1-0-0 with 1-0-1). Due to a limitation in the way we perform shredding of JSONs, we are currently unable to introduce a new
element_content into the Redshift table for support of this new field.
To be clear: you can send link clicks with the new
elementContent attached; these will validate correctly and be stored in Snowplow enriched events (as JSON) correctly; the new field (but not the row) will simply be discarded on its way into Redshift.
You will need to deploy the tables for any new events/context you want to support into your Amazon Redshift database. Make sure to deploy these into the same schema as your
events table resides in.
You can find all Redshift table definitions in our GitHub repository under 4-storage/redshift-storage/sql.
The StorageLoader will automatically pick up the new JSON Paths files – you do not have need to deploy these.