<?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 Re: Join Talend logs / stats tables and custom logging table in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349019#M116045</link>
    <description>&lt;P&gt;Hi @Guy Careau​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can use the *pid columns to create a relationship with your custom log table. In similar scenarios like yours, I usually consider a composite key with pid, father_pid, root_pid and system_pid to create a "stronger" key.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, you need to be careful to avoid duplicated rows. For example: the stats table will always (considering a successful execution of a job) have at least two tuples for the same *pid columns, one for the begin and another for the end of Job execution. You can tell by the message_type column.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Other duplicates might be caused if you enable component statistics. In that case, the origin column will indicate the component and you'll also find a begin and an end tuple for each component execution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore creating a database primary key using the existing columns would not be an option. I guess there will be no problem if you add a custom column to the end of the table with a sequential value, for example, but I never tried it this way.&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jun 2023 20:24:53 GMT</pubDate>
    <dc:creator>anselmopeixoto</dc:creator>
    <dc:date>2023-06-09T20:24:53Z</dc:date>
    <item>
      <title>Join Talend logs / stats tables and custom logging table</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349017#M116043</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I'm using talend integrated logging. The one specified in the project setting. And it's working fine.&lt;/P&gt;&lt;P&gt;But i have another custom logging table for specific purpose. I would like to join the talend's tables and mine with sql.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The talend table have no index, primary key and stuff like that. I can create them but I wonder if it could cause problem with talend if i add extra stuff on it's table?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone already did that ? &lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2023 19:34:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349017#M116043</guid>
      <dc:creator>Careau</dc:creator>
      <dc:date>2023-06-08T19:34:09Z</dc:date>
    </item>
    <item>
      <title>Re: Join Talend logs / stats tables and custom logging table</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349018#M116044</link>
      <description>&lt;P&gt;Hi @Guy Careau​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;​&lt;/P&gt;&lt;P&gt;If you want to join them you have to have a matching column. But if you want to just simply add them like append the schema must match too. so i think maybe you will probably get an error without a matching column.&lt;/P&gt;&lt;P&gt;​&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;​&lt;/P&gt;&lt;P&gt;Vader Out &lt;span class="lia-unicode-emoji" title=":flexed_biceps:"&gt;💪&lt;/span&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 09:31:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349018#M116044</guid>
      <dc:creator>Lord-Vader</dc:creator>
      <dc:date>2023-06-09T09:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: Join Talend logs / stats tables and custom logging table</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349019#M116045</link>
      <description>&lt;P&gt;Hi @Guy Careau​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can use the *pid columns to create a relationship with your custom log table. In similar scenarios like yours, I usually consider a composite key with pid, father_pid, root_pid and system_pid to create a "stronger" key.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, you need to be careful to avoid duplicated rows. For example: the stats table will always (considering a successful execution of a job) have at least two tuples for the same *pid columns, one for the begin and another for the end of Job execution. You can tell by the message_type column.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Other duplicates might be caused if you enable component statistics. In that case, the origin column will indicate the component and you'll also find a begin and an end tuple for each component execution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore creating a database primary key using the existing columns would not be an option. I guess there will be no problem if you add a custom column to the end of the table with a sequential value, for example, but I never tried it this way.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 20:24:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349019#M116045</guid>
      <dc:creator>anselmopeixoto</dc:creator>
      <dc:date>2023-06-09T20:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: Join Talend logs / stats tables and custom logging table</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349020#M116046</link>
      <description>&lt;P&gt;Yes I know that I can use the *pid column for joining my table and talend's.&lt;/P&gt;&lt;P&gt;But my question is can I create an index on the pid's column someting like &lt;/P&gt;&lt;P&gt;alter table TALEND_STAT add constraint TALEND_STAT_PK primary key ( PID);&lt;/P&gt;&lt;P&gt;as well as a constraint.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the talend's logging ans statistic table will containt thousand of rows. &lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2023 12:40:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Join-Talend-logs-stats-tables-and-custom-logging-table/m-p/2349020#M116046</guid>
      <dc:creator>Careau</dc:creator>
      <dc:date>2023-06-12T12:40:29Z</dc:date>
    </item>
  </channel>
</rss>

