<?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: Facing Issue when fields are more for SCD type 2 with TOS SCD components in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236517#M25210</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;as variant too many columns and/or columns names too long&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;65k it is a java limit for code module, with many columns AND long names it could happen&lt;/P&gt;
&lt;P&gt;try to revise columns set, do all must be tracked as SCD?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cheers&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jun 2020 14:10:26 GMT</pubDate>
    <dc:creator>vapukov</dc:creator>
    <dc:date>2020-06-26T14:10:26Z</dc:date>
    <item>
      <title>Facing Issue when fields are more for SCD type 2 with TOS SCD components</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236515#M25208</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to do SCD type 2 on mysql tables using TOS SCD components. But getting error stating -&amp;nbsp;&lt;/P&gt;&lt;P&gt;"The code of tDBInput_1Process(Map&amp;lt;String,Object) is exceeding the 65535 bytes limit".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please suggest what is the solution for this issue.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 08:46:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236515#M25208</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-06-26T08:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Facing Issue when fields are more for SCD type 2 with TOS SCD components</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236516#M25209</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;as variant too many columns and/or columns names too long&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;65k it is a java limit for code module, with many columns AND long names it could happen&lt;/P&gt;
&lt;P&gt;try to revise columns set, do all must be tracked as SCD?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cheers&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 14:10:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236516#M25209</guid>
      <dc:creator>vapukov</dc:creator>
      <dc:date>2020-06-26T14:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Facing Issue when fields are more for SCD type 2 with TOS SCD components</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236517#M25210</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;as variant too many columns and/or columns names too long&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;65k it is a java limit for code module, with many columns AND long names it could happen&lt;/P&gt;
&lt;P&gt;try to revise columns set, do all must be tracked as SCD?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cheers&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 14:10:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Facing-Issue-when-fields-are-more-for-SCD-type-2-with-TOS-SCD/m-p/2236517#M25210</guid>
      <dc:creator>vapukov</dc:creator>
      <dc:date>2020-06-26T14:10:26Z</dc:date>
    </item>
  </channel>
</rss>

