Skip to content

Add table-key-properties to key_property#72

Open
EmaLoprevite wants to merge 1 commit into
singer-io:masterfrom
EmaLoprevite:fix-key_property
Open

Add table-key-properties to key_property#72
EmaLoprevite wants to merge 1 commit into
singer-io:masterfrom
EmaLoprevite:fix-key_property

Conversation

@EmaLoprevite

Copy link
Copy Markdown

Description of change

Allow table-key-properties to be added to the metadata and put into key_property in the SCHEMA, this way a target will be able to read the primary keys.

Manual QA steps

  • Run the tap and look at the final SCHEMA.

Risks

  • None, if table-key-properties is not defined, it will default to [].

Rollback steps

  • Revert this branch.

Allow `table-key-properties` to be added to the metadata and put into `key_property` in the SCHEMA, this way a target will be able to read the primary keys.

@ilkkapeltola ilkkapeltola left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a good solution to the problem.

@ilkkapeltola

Copy link
Copy Markdown

@kspeer825 could you have a look at this. This PR would make the tap significantly more useful when the target knows which primary keys to use in reports. Without this, I cannot load into Snowflake as there's no information on primary keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants