[AP-680] Fastsync tables with composite primary key #400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
CREATE TABLE
statements not generated correctly by fastsync if table has composite key. The only reason why fastsync is still working with tables with composite PKs is that Snowflake and Redshift don't enforce primary keys.Fixing it to generate DDLs with composite PKs correctly.
Checklist
setup.py
is an individual PR and not mixed with feature or bugfix PRs[AP-NNNN]
if applicable. AP-NNNN = JIRA IDAP-NNN
if applicable. AP-NNN = JIRA ID