<?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 Dynamic Input and Output schemas in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Dynamic-Input-and-Output-schemas/m-p/2282645#M56775</link>
    <description>HI, 
&lt;BR /&gt;We have a scenario where in the input files are without headers and each file can have a different column structure(different column numbers and different columns). The schema for each input file is stored in a table based on the fileid (which we are aware of and can pass as a parameter to the job to retrieve the column schema from the table while processing). 
&lt;BR /&gt;Each of these files have certain column like GenderId, LocationId, etc which have to be resolved to their names from their respective lookup table and looked up data loaded into another file. 
&lt;BR /&gt;The table also includes a column which will indicate if the column has another crosswalk table to refer to (e.g. for resolving the gender, Location Names, etc). Number of tmaps is unknown as the cross walk can be different for each file type. 
&lt;BR /&gt;I believe this requires custom coding but wanted to check if there are any thoughts on how the files can be read based on the input schema in the table, the crosswalk referenced column resolved to their names and the file finally loaded into a output file. 
&lt;BR /&gt; 
&lt;BR /&gt; 
&lt;U&gt;Input File Format:&lt;/U&gt; 
&lt;BR /&gt;&amp;nbsp;Jon,M,AL,10000 
&lt;BR /&gt;Alice,F,FL,20000 
&lt;BR /&gt;Jane,F,KS,30000 
&lt;BR /&gt;Smith,M,CA,40000 
&lt;BR /&gt;&amp;nbsp; 
&lt;BR /&gt; 
&lt;U&gt;Table: Schema_Mapper:&lt;/U&gt; 
&lt;BR /&gt; 
&lt;TABLE&gt; 
 &lt;TBODY&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;Fileid&lt;/TD&gt; 
   &lt;TD&gt;ColumnName&lt;/TD&gt; 
   &lt;TD&gt;Has_Crosswalk&lt;/TD&gt; 
   &lt;TD&gt;Crosswalk&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;Name&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;Gender&lt;/TD&gt; 
   &lt;TD&gt;Y&lt;/TD&gt; 
   &lt;TD&gt;Gender_Crosswalk&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;Location&lt;/TD&gt; 
   &lt;TD&gt;Y&lt;/TD&gt; 
   &lt;TD&gt;Location_Crosswalk&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;salary&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
  &lt;/TR&gt; 
 &lt;/TBODY&gt; 
&lt;/TABLE&gt;&amp;nbsp; 
&lt;BR /&gt; 
&lt;U&gt;Table: Gender_CrossWalk:&lt;/U&gt; 
&lt;BR /&gt; 
&lt;TABLE&gt; 
 &lt;TBODY&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;&lt;U&gt;Key&lt;/U&gt;&lt;/TD&gt; 
   &lt;TD&gt;&lt;U&gt;value&lt;/U&gt;&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;&lt;U&gt;M&lt;/U&gt;&lt;/TD&gt; 
   &lt;TD&gt;&lt;U&gt;Male&lt;/U&gt;&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;&lt;U&gt;F&lt;/U&gt;&lt;/TD&gt; 
   &lt;TD&gt;&lt;U&gt;Female&lt;/U&gt;&lt;/TD&gt; 
  &lt;/TR&gt; 
 &lt;/TBODY&gt; 
&lt;/TABLE&gt; 
&lt;U&gt;&amp;nbsp;&lt;/U&gt; 
&lt;BR /&gt; 
&lt;U&gt;Table: Location_CrossWalk:&lt;/U&gt; 
&lt;BR /&gt; 
&lt;TABLE&gt; 
 &lt;TBODY&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;Key&lt;/TD&gt; 
   &lt;TD&gt;Value&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;AL&lt;/TD&gt; 
   &lt;TD&gt;Alabama&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;CA&lt;/TD&gt; 
   &lt;TD&gt;California&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;FL&lt;/TD&gt; 
   &lt;TD&gt;Florida&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;KS&lt;/TD&gt; 
   &lt;TD&gt;Kansas&lt;/TD&gt; 
  &lt;/TR&gt; 
 &lt;/TBODY&gt; 
&lt;/TABLE&gt; 
&lt;BR /&gt;What is needed: 
&lt;BR /&gt;Fileid is known before the run of file. 
&lt;BR /&gt;File has to read the input schema from the table Schema_Mapper, check if the column is a cross walk, join the column value with the cross walk table and generate the output.&amp;nbsp; 
&lt;BR /&gt;The final output file should be as below: 
&lt;BR /&gt;Jon,Male,Alabama,10000 
&lt;BR /&gt;Alice,Female,Florida,20000 
&lt;BR /&gt;Jane,Female,Kansas,30000 
&lt;BR /&gt;Smith,Male,California,40000 
&lt;BR /&gt;Thank You!</description>
    <pubDate>Sat, 16 Nov 2024 11:13:38 GMT</pubDate>
    <dc:creator>_AnonymousUser</dc:creator>
    <dc:date>2024-11-16T11:13:38Z</dc:date>
    <item>
      <title>Dynamic Input and Output schemas</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Dynamic-Input-and-Output-schemas/m-p/2282645#M56775</link>
      <description>HI, 
&lt;BR /&gt;We have a scenario where in the input files are without headers and each file can have a different column structure(different column numbers and different columns). The schema for each input file is stored in a table based on the fileid (which we are aware of and can pass as a parameter to the job to retrieve the column schema from the table while processing). 
&lt;BR /&gt;Each of these files have certain column like GenderId, LocationId, etc which have to be resolved to their names from their respective lookup table and looked up data loaded into another file. 
&lt;BR /&gt;The table also includes a column which will indicate if the column has another crosswalk table to refer to (e.g. for resolving the gender, Location Names, etc). Number of tmaps is unknown as the cross walk can be different for each file type. 
&lt;BR /&gt;I believe this requires custom coding but wanted to check if there are any thoughts on how the files can be read based on the input schema in the table, the crosswalk referenced column resolved to their names and the file finally loaded into a output file. 
&lt;BR /&gt; 
&lt;BR /&gt; 
&lt;U&gt;Input File Format:&lt;/U&gt; 
&lt;BR /&gt;&amp;nbsp;Jon,M,AL,10000 
&lt;BR /&gt;Alice,F,FL,20000 
&lt;BR /&gt;Jane,F,KS,30000 
&lt;BR /&gt;Smith,M,CA,40000 
&lt;BR /&gt;&amp;nbsp; 
&lt;BR /&gt; 
&lt;U&gt;Table: Schema_Mapper:&lt;/U&gt; 
&lt;BR /&gt; 
&lt;TABLE&gt; 
 &lt;TBODY&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;Fileid&lt;/TD&gt; 
   &lt;TD&gt;ColumnName&lt;/TD&gt; 
   &lt;TD&gt;Has_Crosswalk&lt;/TD&gt; 
   &lt;TD&gt;Crosswalk&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;Name&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;Gender&lt;/TD&gt; 
   &lt;TD&gt;Y&lt;/TD&gt; 
   &lt;TD&gt;Gender_Crosswalk&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;Location&lt;/TD&gt; 
   &lt;TD&gt;Y&lt;/TD&gt; 
   &lt;TD&gt;Location_Crosswalk&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;1&lt;/TD&gt; 
   &lt;TD&gt;salary&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
   &lt;TD&gt;&amp;nbsp;&lt;/TD&gt; 
  &lt;/TR&gt; 
 &lt;/TBODY&gt; 
&lt;/TABLE&gt;&amp;nbsp; 
&lt;BR /&gt; 
&lt;U&gt;Table: Gender_CrossWalk:&lt;/U&gt; 
&lt;BR /&gt; 
&lt;TABLE&gt; 
 &lt;TBODY&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;&lt;U&gt;Key&lt;/U&gt;&lt;/TD&gt; 
   &lt;TD&gt;&lt;U&gt;value&lt;/U&gt;&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;&lt;U&gt;M&lt;/U&gt;&lt;/TD&gt; 
   &lt;TD&gt;&lt;U&gt;Male&lt;/U&gt;&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;&lt;U&gt;F&lt;/U&gt;&lt;/TD&gt; 
   &lt;TD&gt;&lt;U&gt;Female&lt;/U&gt;&lt;/TD&gt; 
  &lt;/TR&gt; 
 &lt;/TBODY&gt; 
&lt;/TABLE&gt; 
&lt;U&gt;&amp;nbsp;&lt;/U&gt; 
&lt;BR /&gt; 
&lt;U&gt;Table: Location_CrossWalk:&lt;/U&gt; 
&lt;BR /&gt; 
&lt;TABLE&gt; 
 &lt;TBODY&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;Key&lt;/TD&gt; 
   &lt;TD&gt;Value&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;AL&lt;/TD&gt; 
   &lt;TD&gt;Alabama&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;CA&lt;/TD&gt; 
   &lt;TD&gt;California&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;FL&lt;/TD&gt; 
   &lt;TD&gt;Florida&lt;/TD&gt; 
  &lt;/TR&gt; 
  &lt;TR&gt; 
   &lt;TD&gt;KS&lt;/TD&gt; 
   &lt;TD&gt;Kansas&lt;/TD&gt; 
  &lt;/TR&gt; 
 &lt;/TBODY&gt; 
&lt;/TABLE&gt; 
&lt;BR /&gt;What is needed: 
&lt;BR /&gt;Fileid is known before the run of file. 
&lt;BR /&gt;File has to read the input schema from the table Schema_Mapper, check if the column is a cross walk, join the column value with the cross walk table and generate the output.&amp;nbsp; 
&lt;BR /&gt;The final output file should be as below: 
&lt;BR /&gt;Jon,Male,Alabama,10000 
&lt;BR /&gt;Alice,Female,Florida,20000 
&lt;BR /&gt;Jane,Female,Kansas,30000 
&lt;BR /&gt;Smith,Male,California,40000 
&lt;BR /&gt;Thank You!</description>
      <pubDate>Sat, 16 Nov 2024 11:13:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Dynamic-Input-and-Output-schemas/m-p/2282645#M56775</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2024-11-16T11:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Input and Output schemas</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Dynamic-Input-and-Output-schemas/m-p/2282646#M56776</link>
      <description>Hi,
&lt;BR /&gt;Are you looking for Talend 
&lt;FONT size="2"&gt;&lt;FONT face="Calibri"&gt;dynamic schema feature which allows you to design schema with an unknown column structure (unknown name and number of columns).&lt;/FONT&gt;&lt;/FONT&gt;
&lt;BR /&gt;
&lt;FONT size="2"&gt;&lt;FONT face="Calibri"&gt;Could you please take a look at document about &lt;A href="https://help.talend.com/pages/viewpage.action?pageId=190513179" target="_blank" rel="nofollow noopener noreferrer"&gt;TalendHelpCenter:How to process changing data structure?&lt;/A&gt; to see if it is satisfying your needs?&lt;/FONT&gt;&lt;/FONT&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;FONT size="2"&gt;&lt;FONT face="Calibri"&gt;Best regards&lt;/FONT&gt;&lt;/FONT&gt;
&lt;BR /&gt;
&lt;FONT size="2"&gt;&lt;FONT face="Calibri"&gt;Sabrina&lt;BR /&gt;&lt;/FONT&gt;&lt;/FONT&gt;</description>
      <pubDate>Mon, 18 May 2015 08:25:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Dynamic-Input-and-Output-schemas/m-p/2282646#M56776</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-05-18T08:25:20Z</dc:date>
    </item>
  </channel>
</rss>

