search

k2v-academy / K2View-Academy

Other
0 stars 0 forks source link

Fabric LUI schema change behavior #1070

Closed pWIqmFHmGnqqlIyFDwZIlw1JWRHoo8AgicH1IWD closed 3 months ago

pWIqmFHmGnqqlIyFDwZIlw1JWRHoo8AgicH1IWD commented 3 months ago

How does Fabric know there is a change in schema of an LU? Is it based on some hash? by comparing table by table, column by column?

How will a Fabric GET command behave in following scenarios? Assume it is in SYNC OFF mode.

  1. LU was deployed but there was NO* change in schema
  2. LU was deployed following a change in schema (eg: new column was added)
  3. LU was deployed with a schema change but before we refresh the LUIs, the schema change was reverted, and LU was deployed again

My fabric version is v6.5.9_HF19 but will any of this behavior change with newer versions?

tZajFGR0CidT8AVERBHw8puD36HY6oWViykmIIb commented 3 months ago

Please see the following article which describers the sync behavior: here.

Schema change are considered any change such as add or delete a column, rename table, add or delete table, change column type. Assuming these changes have been deployed. This behavior has been in the system for many versions and is not changing in the newer versions.

pWIqmFHmGnqqlIyFDwZIlw1JWRHoo8AgicH1IWD commented 3 months ago

Hi Nataly,

The article talks about sync behavior. How does Fabric know there is a change in schema of an LU? Is it based on some hash? by comparing table by table, column by column? Also, will it apply schema changes to an LUI if LU was deployed with a schema change but before we resync that LUI, the schema change was reverted, and LU was deployed again?