topic Re: Token properties file for BigQuery access across multiple jobs in Talend Studio

Token properties file for BigQuery access across multiple jobs

Anonymous — Sat, 16 Nov 2024 10:31:53 GMT

Just checking but I assume that if I use the same Client Id/Client Secret to execute queries in multiple jobs that may be run at different times then I should make sure that any such jobs store there authorization token in the same "token properties File Name" on the Advanced Settings dialog?
TIA, M

Re: Token properties file for BigQuery access across multiple jobs

Anonymous — Wed, 06 Jul 2016 03:54:00 GMT

Hi,
Are you looking for "Context" feature in talend?
Could you please take a look at: https://help.talend.com/search/all?query=Using+contexts+and+variables to see if it can meet your needs?
More information about your job requirement will be preferred.

Best regards
Sabrina

Re: Token properties file for BigQuery access across multiple jobs

Anonymous — Wed, 06 Jul 2016 09:25:03 GMT

Hi - sorry, no, perhaps my question wasn't clear. As I understand it, the jobs run using a client id, client secret and an authorization code which is obtained by getting a token from google using the url that is displayed when you first run the job. My assumption is that this is a transient token and gets renewed after a certain period and that it is this that is stored in the token.properties file defined on the advanced dialog? If I then use the same credentials in multiple separate jobs that may run entirely independently of each other I assume I should make sure that the path to the token.properties file is identical (I use a context variable for this already) as if not when one job requests and stores a new token, the following job trying to use the same credentials will fail - am I wrong?
M

Re: Token properties file for BigQuery access across multiple jobs

Anonymous — Thu, 14 Jul 2016 10:34:43 GMT

Can you confirm?