Support For Google Big Query In Australia Region With ODBC Driver x.x.x.1011
We have a prospect who made a decision on purchasing Qlik Replicate (pending procurement), interested in Google Big Query target endpoint. The issue we have is that it was confirmed Qlik Replicate only supports ODBC version x.x.x.1000 at current time, with the 'location' set only to US and EU. As part of the POC, they were able to perform tests scenario using different ODBC driver and the latest one came very close to performing flawlessly.
Initially when they performed tests using ODBC x.x.x.1007, the prospect was able to see that Replicate cannot use the driver version because the driver was not correctly giving regional information as the information is sent back and forth. On this driver, prospect was able to see that the Location option in the Replicate endpoint setting is not as relevant. This was sent over to Google to see if they can improve upon the issue as we understand that it is a problem on the ODBC driver side.
Going forward to this time, Google listened to prospect feedback and release ODBC Driver x.x.x.1011, which contain an important patch that correctly resolves the location issue in the driver. Using this driver, Replicate flawlessly performs CDC even if the endpoint setting is set to US, while the data set itself is Australia based. The catch here is that, after roughly an hour of task runtime, Replicate fails to reauthenticate giving out a 'file not found' error. It was seen that Replicate authenticates through using GCP with a JSON file and then purges such JSON file. But at one point, Replicate tries to reauthenticate and the process fails because the file that it needed was already purged. Maybe there ia an authentication time out that we are not aware of.
What I want to concentrate on however, is that the 'Location' under Replicate setting may not be necessary under the latest ODBC driver. Another point that was brought up, was that ODBC driver x.x.x.1000 is not available from the official link from Google:
The ETA implementation starting date is 12th of June. It is critical for us to have this supported, otherwise we need to return to the drawing board and the decision of Qlik Replicate purchase may be reversed.
