Sounds right to me. I wonder if they have a concern that the column name used for the BigQuery row key might conflict with names of app columns. They’ll be introducing a new column name, and need to avoid conflicts. I can imagine other edge-case concerns, too.
Hello all,
I just read that they are discussing the details of how to safely incorporate the missing data into the BigQuery schema.
I am assuming they received your suggestion but just in case I will add it to the ticket as well.
@Jose_Arteaga Hope you are keeping well with all the movement on forums.
May I ask why the team has failed to update me on mail or keep me in loop with proceedings, the Export to Big Query was a feature my client needed and therefore opted for Enterprise License. I do beleive they should be fixing this urgently as it is an advertised feature for Enterprise. Please ask them to provide an ETA for fix via email.
Of course! I am contacting the support team asking for an update.
@Jose_Arteaga , what’s word on this?
@Steve Latest update last night.
Hello @Denzil_Snyman, I completely understand your frustration regarding this delay. I have reached out to our engineering team to expedite the analysis process and ensure this is addressed as quickly as possible. I truly appreciate your patience and will be sure to keep you updated as I receive more information.