Hi Team!
It seems that the current state of the Google Big Query requires that the connector to be re-authorized in order to refresh the views and fields available to the connector. This is not ideal as it makes changing and validating the ingestion of data into Gainsight very cumbersome and manual.
The idea is that going forward it would be great if refreshing the available views/fields was automatic like with other connectors.
Thanks!
-Will
This should definitely be considered a bug. The authorization token already gives the connector the rights to query the tables. There’s no need to request a new token to refresh the tables.
Furthermore, this is very disruptive as an authorized admin needs to go the extra length to authenticate as the service account authorized for this job. Doing that on a prod environment just to refresh a schema is just not what any respectable organization expects to do.
Hi Folks, any update on this? Increasingly seeing this for other customers that are using BigQuery.
It’s a pain to reauthorize every time for once big query table is updated. And reauthorizing is not working every time
We are just now starting to explore the conversion of our current integration strategy to Big Query. This issue definitely makes me a bit nervous about the change. I would agree that this is a bug in my mind. I would be concerned about developers not being aware of new fields or changes to fields and have it cause issues.
Any update here?
I haven’t received any update from GS regarding this issue. We’re still required to re-authorize the connector to retrieve the updated schema.
Ran into this issue the other day. Our use of this connector is gated by a schema of views, which expressed this same issue.
Our team was able to drop the specific view and recreate it and the GS connector picked up those changes without having to re-authorize the GS connector.
Editing the view didn’t populate the changes via the GS connector, but we could also see that the schema metadata in BigQuery for the view was not updating, even though you could query all the new fields just fine. Assuming this weird state is related.
Sharing in the hopes that this helps someone … =)