Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
TTH1
Contributor II
Contributor II

Select Change table header column should be removed from delta file

Hi All,

While creating in delta file I have turned on store changes processing after that I have uncheck the below option because I don't  want this column in my output file

change_seq

change_oper

change_mask

............

But still this header is showing in file there would be no data. I dont want these column in my file

Please help me 

Labels (2)
1 Solution

Accepted Solutions
john_wang
Support
Support

Hello @TTH1 ,

Welcome to the community.

I'm not sure which target endpoint it is, in my test labs, Replicate works fine with the Oracle target, however please take note that the "Change Table Creation" options should set to "DROP and CREATE" if the store change table exist already, the sample screen:

john_wang_0-1686929059341.png

BTW, the first 2 columns are the store change table primary key columns, remove them leads warnings in design stage:

john_wang_1-1686929173211.png

In runtime stage got warning too:

All change tables will be created without a unique index. As a result if tables contain lob columns they will be dropped form the change tables.

it's recommended to keep the 2 columns, they are helpful while your apps consuming the table data.

Regards,

John.

 

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

4 Replies
john_wang
Support
Support

Hello @TTH1 ,

Welcome to the community.

I'm not sure which target endpoint it is, in my test labs, Replicate works fine with the Oracle target, however please take note that the "Change Table Creation" options should set to "DROP and CREATE" if the store change table exist already, the sample screen:

john_wang_0-1686929059341.png

BTW, the first 2 columns are the store change table primary key columns, remove them leads warnings in design stage:

john_wang_1-1686929173211.png

In runtime stage got warning too:

All change tables will be created without a unique index. As a result if tables contain lob columns they will be dropped form the change tables.

it's recommended to keep the 2 columns, they are helpful while your apps consuming the table data.

Regards,

John.

 

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
MoeE
Partner - Specialist
Partner - Specialist

Hi John,

Is there a particular reason as to why the "Change Table Creation" options should set to "DROP and CREATE" if the store change table exist already?

Kind regards,

Mohammed

john_wang
Support
Support

Hello Mohammed @MoeE ,

Just to make sure the metadata is aligned.

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
MoeE
Partner - Specialist
Partner - Specialist

Hi John, 

Thank you. Can you please elaborate a little for me? 

Regards,

Mohammed