I am trying to understand how people use snowplow unstructured events with big query. Right now I see that it adds something like
contexts_org_w3_performance_timing_1_0_0 which has the version number in the record. What happens if there is a bump in that version number to something like 1_0_1 I would expect to see
contexts_org_w3_performance_timing_1_0_1 and I would no longer get any data in the
contexts_org_w3_performance_timing_1_0_0 record. This means that if I build any reports with the
1_0_0 name in them, they will be broken until I can edit them to coalesce between the
1_0_1 columns. Is there any way to make the record something like
1_0 instead and by convention only add columns to the record if we increment the patch, but then create a new record column if we increment the minor version?
I am just trying to figure out how best to make this future proof as much as possible before we start depending on it too much.