<?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: Chaining of schema loads in Data &amp; Schema Discussions</title>
    <link>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3150#M223</link>
    <description>&lt;P&gt;Thanks for the information. We are on Incorta version 5.1.5 as of now.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Nov 2022 13:25:23 GMT</pubDate>
    <dc:creator>sushant_lkq</dc:creator>
    <dc:date>2022-11-03T13:25:23Z</dc:date>
    <item>
      <title>Chaining of schema loads</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3024#M207</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;We have this specific requirement where we want to create a workflow for schema loads. For example Schema B load should happen only after schema A is loaded and so on. As a workaround we can setup appropriate schedule timing for each schema but offcourse it won't guarantee this behaviour .&lt;/P&gt;&lt;P&gt;Has anyone faced and achieved this in Incorta?&lt;/P&gt;&lt;P&gt;Thanks for your support!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sushant&lt;/P&gt;</description>
      <pubDate>Sat, 22 Oct 2022 07:14:29 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3024#M207</guid>
      <dc:creator>sushant_lkq</dc:creator>
      <dc:date>2022-10-22T07:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: Chaining of schema loads</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3032#M208</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.incorta.com/t5/user/viewprofilepage/user-id/553"&gt;@sushant_lkq&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;It depends on which version of Incorta you have?&lt;/P&gt;&lt;P&gt;For on-prem/older releases, you can use the &lt;A href="https://docs.incorta.com/5.1/tools-cli" target="_self"&gt;CLI python scripts.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For coming/recent/cloud versions, there are public APIs are currently in Beta, which can help to integrate with some scripts or tools like AirFlow for example.&lt;/P&gt;&lt;P&gt;And later on, there's a feature on the &lt;A href="http://Scheduled%20load plans with multiple schemas" target="_self"&gt;roadmap,&lt;/A&gt;&amp;nbsp;that would allow scheduling multiple schemas from the scheduler, and it will respect the dependency between them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which Incorta version do you have?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 12:35:02 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3032#M208</guid>
      <dc:creator>Prince</dc:creator>
      <dc:date>2022-10-25T12:35:02Z</dc:date>
    </item>
    <item>
      <title>Re: Chaining of schema loads</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3050#M209</link>
      <description>&lt;P&gt;Here's an idea ( and yes, it's a kludge &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;1) Go to the CMC and set the loader to fail on first error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) Change the load order of your schema so that a "test" table is first and in its own group&lt;/P&gt;&lt;P&gt;3) Write test table so it fails if the predecessor load hasn't completed for that day&amp;nbsp; --&amp;nbsp; I don't know the details here, but it looks like you could call a stored proc based on the Incorta metadata load and force that fail if the last load date &amp;lt;&amp;gt; current_date or something like that&amp;nbsp;&lt;/P&gt;&lt;P&gt;4) Schedule the schema load to run every n-minutes.&amp;nbsp; &amp;nbsp;If the first table fails, the load will not continue, if it does not fail it will.&amp;nbsp; &amp;nbsp; If you were really ambitious you could include timestamps in the logic to force the test table to fail if it had already run successfully that day or w/in whatever cadence you are aiming for.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or wait for the roadmaped enhancements&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But if you do fiddle around w/ this idea please post back as I'm curious to see if it could work.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 20:43:25 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3050#M209</guid>
      <dc:creator>RADSr</dc:creator>
      <dc:date>2022-10-26T20:43:25Z</dc:date>
    </item>
    <item>
      <title>Re: Chaining of schema loads</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3150#M223</link>
      <description>&lt;P&gt;Thanks for the information. We are on Incorta version 5.1.5 as of now.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 13:25:23 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3150#M223</guid>
      <dc:creator>sushant_lkq</dc:creator>
      <dc:date>2022-11-03T13:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: Chaining of schema loads</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3156#M224</link>
      <description>&lt;P&gt;Do you have any documentation on how to do this with python scripts in CLI?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 20:27:45 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/chaining-of-schema-loads/m-p/3156#M224</guid>
      <dc:creator>kxie</dc:creator>
      <dc:date>2022-11-03T20:27:45Z</dc:date>
    </item>
  </channel>
</rss>

