Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize Write Mode to Merge for All Tables to Ensure Data Integrity and Avoid Duplication #1240

Open
SouravSaxena3200 opened this issue Jun 18, 2024 · 1 comment
Labels
user_question Questions coming from users

Comments

@SouravSaxena3200
Copy link

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.

@SouravSaxena3200 SouravSaxena3200 added the user_question Questions coming from users label Jun 18, 2024
@gueniai
Copy link
Contributor

gueniai commented Jun 25, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user_question Questions coming from users
Projects
None yet
Development

No branches or pull requests

2 participants