Snowplow 0.5.1 released, with lots of small improvements
We have just released Snowplow 0.5.1! Rather than one large new feature, version 0.5.1 is an incremental release which contains lots of small fixes and improvements to the ETL and storage sub-systems. The two big themes of these updates are:
- Improving the robustness of the ETL process
- Laying the foundations for loading Snowplow events into Infobright Community Edition (ICE)
To take each of these themes in turn:
1. A more robust ETL process
Firstly, the Hive deserializer is now setup to log warnings (rather than die) on non-critical data quality issues.
Additionally, there is now an option (switched off by default) to continue processing even on unexpected row-level errors (such as an input file not matching the expected CloudFront format). We have added a configuration option to the EmrEtlRunner’s configuration file to support this:
:etl: :continue_on_unexpected_error: false
Switch this to ‘true’ to continue processing on unexpected row-level errors.
2. Groundwork for Infobright compatibility
We have added a table definition (and supporting scripts) for setting up a Snowplow events table in Infobright - you can find these in the main repository under
Some early ETL design decisions meant that the Snowplow event files being generated before 0.5.1 were not compatible with being loaded into Infobright (or similar relational databases like Postgres or MySQL). We have made some updates to the ETL process in 0.5.1 to fix this:
- In the Hive deserializer, we now convert tabs to 4 spaces to prevent a stray tab from breaking our load into Infobright
- Databases like Infobright don’t support Hive’s
ARRAY<STRING>syntax, so we have updated the Hive deserializer to also output individual booleans for the browser features, alongside the browser features array
- We have created a new HiveQL script which outputs Snowplow event files in a format which can be easily loaded into Infobright - this is called
- We have added a configuration option to the EmrEtlRunner’s configuration file so that you can choose whether to output Hive-format or non-Hive-format event files
On point 4: we believe that most people will want to load their Snowplow event files into other database systems, such as Infobright (or eventually, Postgres, Google BigQuery, SkyDB etc). Therefore, the default setting for the configuration option in the EmrEtlRunner is to output your Snowplow event files in the non-Hive-format:
:etl: :storage_format: non-hive
As the comment says, if you will only be doing analysis in Hive, you could switch this setting to ‘hive’ and benefit from the slightly-tweaked, Hive-friendly file format.
In the pipeline
At Snowplow we want to support multiple different storage and analytics options for Snowplow events, alongside our current Hive-based approach. This version 0.5.1 provides the building blocks for our Infobright support - for the next release, we are working on a Storage Loader component to download your event files from Amazon S3 and load them into your local Infobright instance. We’ll keep you posted on our progress here!