Skip to content

Conversation

@hg-ramosaj
Copy link

  • Added logging for deleted tables
  • allowed insertion_method_tables to take stream names

README.md Outdated
| validate_records | Boolean | | (Default: False) Validate every single record message to the corresponding JSON schema. This option is disabled by default and invalid RECORD messages will fail only at load time by Postgres. Enabling this option will detect invalid records earlier but could cause performance degradation. |
| temp_dir | String | | (Default: platform-dependent) Directory of temporary CSV files with RECORD messages. |
| insertion_method | String | | (Default: 'incremental') Currently only handles 'truncate' (drop and re-create table before adding rows) and 'incremental' (upsert new rows) |
<<<<<<< HEAD
Copy link
Member

Choose a reason for hiding this comment

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

Looks like there's a conflict here

README.md Outdated
| insertion_method_tables | Array(String) | | (Default: []) Names of streams corresponding to tables to apply "insertion method" to. Has no effect if insertion method not specified. |
=======
| insertion_method_tables | Array(String) | | (Default: []) Tables to apply "insertion method" to. Has no effect if insertion method not specified. |
>>>>>>> 4a18fba3c9a6c759f298e7b1bcc51640d95d2a76
Copy link
Member

Choose a reason for hiding this comment

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

And here

if len(insertion_method_tables) == 0: #if no insertion_method_tables specified, remove all tables and repopulate
self.query(self.drop_table())
elif table_name[1:-1] in insertion_method_tables: #and if table name in insertion_method_tables
elif stream in insertion_method_tables: #and if table name in insertion_method_tables, truncate
Copy link
Member

Choose a reason for hiding this comment

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

Does this mean it will always expect stream name instead of table name? Can we support both?

Copy link
Author

Choose a reason for hiding this comment

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

Yes! I figured it would be clearer in the config to have the stream names instead of the table names, since the table names for postgres are different (underscores, lowercase, etc). We could support both if needed.

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