feat: one json column to rule them all #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RudderStack discards events with more than 200 properties as "Bad Event". This results in droping genuine events sometimes. Also these properties are flattened by default in warehouse, resulting in too many columns sometimes reaching the upper limit of columns in warehouses. A usual challenge faced in collecting data from unstructured or semi-structured webhook data with lots of nested values.
This user transformation is a solution to these challenges.
It enables your data pipeline to store all event properties as single json data type column.
Here, we first move
event.properties
tocontext.properties
and then setjsonPaths
option totrack.context.proprerties
. This instructs RudderStack to not flattencontext.proprerties
oftrack
events and store that as json data type column.More info - https://www.rudderstack.com/docs/destinations/warehouse-destinations/json-column-support/