You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that in the consumer database, some tables are written using the append mode, while others use the merge mode. To reduce data duplication and improve data integrity, can we standardize the write mode to merge for all tables? Alternatively, introducing a configuration flag during the run to specify whether all tables should use the default mode or be forced into merge mode would provide greater flexibility and control over the data management process.
The text was updated successfully, but these errors were encountered:
Hi @SouravSaxena3200! Thank you for the suggestion! The tables have been deliberately designed the way they are. Utilizing the correct write mode allows us to create pipelines that are as performant as possible.
These should not lead to any duplication or data integrity issues, have you noticed anything of the sort?
I have noticed that in the consumer database, some tables are written using the append mode, while others use the merge mode. To reduce data duplication and improve data integrity, can we standardize the write mode to merge for all tables? Alternatively, introducing a configuration flag during the run to specify whether all tables should use the default mode or be forced into merge mode would provide greater flexibility and control over the data management process.
The text was updated successfully, but these errors were encountered: