Timezone isn’t correct for Google BigQuery schema
In Adobe Campaign Classic v8.5, when reading data from the column of a Google BigQuery table defined as datetimetz at the schema level, if the displayed date and hour don’t include the operator’s timezone information, add the option useTimestampTZ and set it to 1.
Description description
Environment
Campaign Classic v8.5
Issue/Symptoms
When reading data from a Google BigQuery table defined as datetimetz at the schema level, the displayed date and hour don’t include the operator’s timezone information.
Steps to reproduce:
-
Define a new schema with Google BigQuery as the source of data.
-
Define a new attribute with the type
datetimetz. -
Read data from this schema in a workflow.
-
Check the output of the date field previously defined; you can see that the timezone of the operator isn’t taken into account.
Resolution resolution
To resolve this, add the option useTimestampTZwith value as 1 under the Google BigQuery external account that is being used when creating the schema.
Please note that the web server needs to be restarted for this change to take effect.
Cause:
The useTimestampTZ option is missing in the external account definition.
Ask Questions In Our Experience League Campaign Community
If you have any questions you’d like answered about this topic, or read previous answered-questions, we invite you to view our Experience League Community blog post that includes this article, send us your questions and comments, and join our Experience League Campaign Community!