<?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 Save generic schema in repository in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307445#M78883</link>
    <description>Hello, 
&lt;BR /&gt;I try to use a maximum number of schema in metadata, so I can see how many different schema I use, share them, trace modification and so on. 
&lt;BR /&gt;But I find that actual schema management in repository is not really flexible. In particular, I have two suggestion : 
&lt;BR /&gt;1 - enable a "generic" metadata repository (as it exists DB connections, File Delimited, ect) in which schema could be defined without being attached to a connection or a file ; 
&lt;BR /&gt;2 - add a bouton in property view of component / edges to allow user to save built-in schema to repository ; 
&lt;BR /&gt;Use case for 1 : I have quite a complex built-in schema used as an input of several tMap component. Due to a functionnal requirement, all the tMap have to have the same schema. If I modify one schema (for example add a field), I need to do the same for all other tMap by hand ; 
&lt;BR /&gt;Use case for 2 : I use a repository schema for a component, need to modify it (so it become "built-in"). If I want to save the modification in repository, I have to create a fresh new one schema (or edit an old one), but I can't just update/save as new my built-it schema. 
&lt;BR /&gt;Any remarks appreciated 
&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009MACn.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/154443iC5B8CACEF3D12C6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009MACn.png" alt="0683p000009MACn.png" /&gt;&lt;/span&gt; 
&lt;BR /&gt;Francois</description>
    <pubDate>Sat, 16 Nov 2024 14:37:10 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T14:37:10Z</dc:date>
    <item>
      <title>Save generic schema in repository</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307445#M78883</link>
      <description>Hello, 
&lt;BR /&gt;I try to use a maximum number of schema in metadata, so I can see how many different schema I use, share them, trace modification and so on. 
&lt;BR /&gt;But I find that actual schema management in repository is not really flexible. In particular, I have two suggestion : 
&lt;BR /&gt;1 - enable a "generic" metadata repository (as it exists DB connections, File Delimited, ect) in which schema could be defined without being attached to a connection or a file ; 
&lt;BR /&gt;2 - add a bouton in property view of component / edges to allow user to save built-in schema to repository ; 
&lt;BR /&gt;Use case for 1 : I have quite a complex built-in schema used as an input of several tMap component. Due to a functionnal requirement, all the tMap have to have the same schema. If I modify one schema (for example add a field), I need to do the same for all other tMap by hand ; 
&lt;BR /&gt;Use case for 2 : I use a repository schema for a component, need to modify it (so it become "built-in"). If I want to save the modification in repository, I have to create a fresh new one schema (or edit an old one), but I can't just update/save as new my built-it schema. 
&lt;BR /&gt;Any remarks appreciated 
&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009MACn.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/154443iC5B8CACEF3D12C6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009MACn.png" alt="0683p000009MACn.png" /&gt;&lt;/span&gt; 
&lt;BR /&gt;Francois</description>
      <pubDate>Sat, 16 Nov 2024 14:37:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307445#M78883</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T14:37:10Z</dc:date>
    </item>
    <item>
      <title>Re: Save generic schema in repository</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307446#M78884</link>
      <description>I think you have two good improvements ideas !&lt;BR /&gt;Could you report them in our bugtracker (&lt;A href="http://talendforge.org/bugs" rel="nofollow noopener noreferrer"&gt;http://talendforge.org/bugs&lt;/A&gt;) as feature requests ?</description>
      <pubDate>Thu, 12 Apr 2007 09:23:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307446#M78884</guid>
      <dc:creator>smallet</dc:creator>
      <dc:date>2007-04-12T09:23:12Z</dc:date>
    </item>
    <item>
      <title>Re: Save generic schema in repository</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307447#M78885</link>
      <description>&lt;BLOCKQUOTE&gt; 
 &lt;TABLE border="1"&gt; 
  &lt;TBODY&gt; 
   &lt;TR&gt; 
    &lt;TD&gt;Could you report them in our bugtracker (&lt;A href="http://talendforge.org/bugs" rel="nofollow noopener noreferrer"&gt;http://talendforge.org/bugs&lt;/A&gt;) as feature requests ?&lt;/TD&gt; 
   &lt;/TR&gt; 
  &lt;/TBODY&gt; 
 &lt;/TABLE&gt; 
&lt;/BLOCKQUOTE&gt; 
&lt;BR /&gt;Yes, of, course. 
&lt;BR /&gt; 
&lt;BR /&gt;Between, I found a kind of workaround with the xml import/export of schema. It removes the hard-working of creating again and again field (or coping them), but it do not manage consistency between schema. 
&lt;BR /&gt;Francois</description>
      <pubDate>Thu, 12 Apr 2007 11:18:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Save-generic-schema-in-repository/m-p/2307447#M78885</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-04-12T11:18:38Z</dc:date>
    </item>
  </channel>
</rss>

