<?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 Incremental Loading - how do you use it after 5.1? in Data &amp; Schema Discussions</title>
    <link>https://community.incorta.com/t5/data-schema-discussions/incremental-loading-how-do-you-use-it-after-5-1/m-p/3224#M242</link>
    <description>&lt;P&gt;Hello - we are in the process of upgrading from 5.0 to 5.2 and have noticed a &lt;A href="https://docs.incorta.com/5.1/release-notes#key-column-changes-require-a-full-load-for-the-physical-schema-table" target="_self"&gt;new requirement&lt;/A&gt; in 5.1.&amp;nbsp; Changing a 'Key' column in a physical table now requires a full load of that table.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use incremental loads to load daily snapshots from source systems, and we incrementally load datasets for time-series analysis.&amp;nbsp; Incremental loading also works well with slowly changing dimensions because you can load only changes and let the table build over time.&lt;/P&gt;&lt;P&gt;From my testing, I've found this new requirement to be true for any column, not only a 'Key'.&amp;nbsp; Adding a new measure or dimension will also trigger this warning.&amp;nbsp; (Removing a column does not trigger the warning, but if you remove it and put it back then it does.)&lt;/P&gt;&lt;P&gt;In 5.2, if you add a new column and do not perform a Full Load you will receive an 'Index out of bounds' error on any data selection that includes the new column.&lt;/P&gt;&lt;P&gt;This is a significant restriction to the way incremental loading works.&amp;nbsp; In version 5.0, adding a new column works as expected.&amp;nbsp; The column shows up with null values for prior loads and is populated from when it was added.&amp;nbsp; This even works for adding new keys.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the company philosophy for tables loaded incrementally?&amp;nbsp; They provide tremendous value and it's made Incorta the best way for us to easily view day-over-day changes of datasets.&amp;nbsp; As users perform analysis adding new columns is a normal practice, but losing all your history in the process will usually be unacceptable.&lt;/P&gt;&lt;P&gt;Does anyone know of a workaround for this?&amp;nbsp; Attached are some screenshots of the warnings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 11 Nov 2022 20:30:26 GMT</pubDate>
    <dc:creator>mike_mascitti</dc:creator>
    <dc:date>2022-11-11T20:30:26Z</dc:date>
    <item>
      <title>Incremental Loading - how do you use it after 5.1?</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/incremental-loading-how-do-you-use-it-after-5-1/m-p/3224#M242</link>
      <description>&lt;P&gt;Hello - we are in the process of upgrading from 5.0 to 5.2 and have noticed a &lt;A href="https://docs.incorta.com/5.1/release-notes#key-column-changes-require-a-full-load-for-the-physical-schema-table" target="_self"&gt;new requirement&lt;/A&gt; in 5.1.&amp;nbsp; Changing a 'Key' column in a physical table now requires a full load of that table.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use incremental loads to load daily snapshots from source systems, and we incrementally load datasets for time-series analysis.&amp;nbsp; Incremental loading also works well with slowly changing dimensions because you can load only changes and let the table build over time.&lt;/P&gt;&lt;P&gt;From my testing, I've found this new requirement to be true for any column, not only a 'Key'.&amp;nbsp; Adding a new measure or dimension will also trigger this warning.&amp;nbsp; (Removing a column does not trigger the warning, but if you remove it and put it back then it does.)&lt;/P&gt;&lt;P&gt;In 5.2, if you add a new column and do not perform a Full Load you will receive an 'Index out of bounds' error on any data selection that includes the new column.&lt;/P&gt;&lt;P&gt;This is a significant restriction to the way incremental loading works.&amp;nbsp; In version 5.0, adding a new column works as expected.&amp;nbsp; The column shows up with null values for prior loads and is populated from when it was added.&amp;nbsp; This even works for adding new keys.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the company philosophy for tables loaded incrementally?&amp;nbsp; They provide tremendous value and it's made Incorta the best way for us to easily view day-over-day changes of datasets.&amp;nbsp; As users perform analysis adding new columns is a normal practice, but losing all your history in the process will usually be unacceptable.&lt;/P&gt;&lt;P&gt;Does anyone know of a workaround for this?&amp;nbsp; Attached are some screenshots of the warnings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2022 20:30:26 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/incremental-loading-how-do-you-use-it-after-5-1/m-p/3224#M242</guid>
      <dc:creator>mike_mascitti</dc:creator>
      <dc:date>2022-11-11T20:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: Incremental Loading - how do you use it after 5.1?</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/incremental-loading-how-do-you-use-it-after-5-1/m-p/3293#M243</link>
      <description>&lt;P&gt;This isn't a great workaround, but I do remember a similar problem being addressed and a workaround given here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.incorta.com/t5/data-schema-discussions/schema-full-load-after-changes/m-p/823" target="_blank"&gt;https://community.incorta.com/t5/data-schema-discussions/schema-full-load-after-changes/m-p/823&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Nov 2022 22:02:25 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/incremental-loading-how-do-you-use-it-after-5-1/m-p/3293#M243</guid>
      <dc:creator>BrandonR</dc:creator>
      <dc:date>2022-11-15T22:02:25Z</dc:date>
    </item>
  </channel>
</rss>

