<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Exceptions handling for Google BigQuery as a target in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418231#M9438</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;currently Qlik Replicate doesn't support&amp;nbsp;exceptions table error handling option for BigQuery.&lt;BR /&gt;See&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/replicate/November2023/Content/Replicate/Main/Google%20Cloud%20BigQuery/bigquery_limitations_postgresql_source.htm" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/replicate/November2023/Content/Replicate/Main/Google%20Cloud%20BigQuery/bigquery_limitations_postgresql_source.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;- Are there any plans to support the exceptions table error handling option for BigQuery in Qlik Replicate?&lt;/P&gt;
&lt;P&gt;- Are there some aletrnative methods to handle and track exceptions?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Will error-related information (incl. SQL-Statement) be stored in the log file with the log level set to "trace"?&lt;/P&gt;
&lt;P&gt;For example: when error on insert due to the wrong timestamp format occurs?&lt;/P&gt;
&lt;P&gt;- Any Other ideas?&lt;/P&gt;</description>
    <pubDate>Tue, 13 Feb 2024 12:43:37 GMT</pubDate>
    <dc:creator>vdna101</dc:creator>
    <dc:date>2024-02-13T12:43:37Z</dc:date>
    <item>
      <title>Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418231#M9438</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;currently Qlik Replicate doesn't support&amp;nbsp;exceptions table error handling option for BigQuery.&lt;BR /&gt;See&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/replicate/November2023/Content/Replicate/Main/Google%20Cloud%20BigQuery/bigquery_limitations_postgresql_source.htm" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/replicate/November2023/Content/Replicate/Main/Google%20Cloud%20BigQuery/bigquery_limitations_postgresql_source.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;- Are there any plans to support the exceptions table error handling option for BigQuery in Qlik Replicate?&lt;/P&gt;
&lt;P&gt;- Are there some aletrnative methods to handle and track exceptions?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Will error-related information (incl. SQL-Statement) be stored in the log file with the log level set to "trace"?&lt;/P&gt;
&lt;P&gt;For example: when error on insert due to the wrong timestamp format occurs?&lt;/P&gt;
&lt;P&gt;- Any Other ideas?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 12:43:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418231#M9438</guid>
      <dc:creator>vdna101</dc:creator>
      <dc:date>2024-02-13T12:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418252#M9439</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/285036"&gt;@vdna101&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If the option "&lt;SPAN class="checkboxInnerSpan ng-binding"&gt;Apply changes using SQL MERGE" in Change Processing Tuning is unchecked, then log exception table option will be enabled in Apply Conflicts.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="checkboxInnerSpan ng-binding"&gt;Regards,&lt;BR /&gt;Suresh&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 13:28:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418252#M9439</guid>
      <dc:creator>sureshkumar</dc:creator>
      <dc:date>2024-02-13T13:28:44Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418269#M9441</link>
      <description>&lt;P&gt;Hi Suresh&lt;BR /&gt;attrep_apply_exceptions is currently not supported for the Big Query as a target&amp;nbsp;according to Qlik Replicate Documentation.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 14:03:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2418269#M9441</guid>
      <dc:creator>vdna101</dc:creator>
      <dc:date>2024-02-13T14:03:59Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419018#M9501</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/285036"&gt;@vdna101&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I agree with you, but when we uncheck the option "&lt;SPAN&gt;Apply changes using SQL MERGE", we can set the exception table in Apply&amp;nbsp;&lt;/SPAN&gt;conflicts settings. Kindly test it once.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Suresh&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 01:55:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419018#M9501</guid>
      <dc:creator>sureshkumar</dc:creator>
      <dc:date>2024-02-15T01:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419080#M9507</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/285036"&gt;@vdna101&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Let's say, cannot find a record to update (0 rows affected), the update statement will be logged into the attrep_apply_exception table.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding "&lt;SPAN&gt;The&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ui_item"&gt;Log record to the exceptions table&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;error handling option for Apply Conflicts and Data Errors is not supported.", I think it may be a limitation with using SQL MERGE. I would suggest to create a support ticket to verify with R&amp;amp;D.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Desmond&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 07:06:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419080#M9507</guid>
      <dc:creator>DesmondWOO</dc:creator>
      <dc:date>2024-02-15T07:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419870#M9531</link>
      <description>&lt;P&gt;Hello Suresh and Desmond&lt;BR /&gt;&lt;BR /&gt;thank you very much for your support.&lt;BR /&gt;&lt;BR /&gt;Our test with Qlik Replicate applying changes to Big Query target shows, that the attrep_apply_exception&amp;nbsp;table gets a new error log record (0 rows affected) when an update on a non existing record in the target table occurs. &lt;BR /&gt;&lt;BR /&gt;The real system behavior in that case differs from the documented limitation:&lt;BR /&gt;"The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ui_item"&gt;Log record to the exceptions table&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;error handling option for Apply Conflicts and Data Errors is not supported."&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Best Regards, Vadim&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 09:13:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419870#M9531</guid>
      <dc:creator>vdna101</dc:creator>
      <dc:date>2024-02-16T09:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419892#M9536</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/285036"&gt;@vdna101&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;As the behavior differs from the documentation, I would suggest to create a support ticket to clarify the behavior.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Desmond&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 09:42:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419892#M9536</guid>
      <dc:creator>DesmondWOO</dc:creator>
      <dc:date>2024-02-16T09:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Exceptions handling for Google BigQuery as a target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419908#M9537</link>
      <description>&lt;P&gt;thank you, support ticket created&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 10:06:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Exceptions-handling-for-Google-BigQuery-as-a-target/m-p/2419908#M9537</guid>
      <dc:creator>vdna101</dc:creator>
      <dc:date>2024-02-16T10:06:21Z</dc:date>
    </item>
  </channel>
</rss>

