Handling Renamed Fields in Google Drive CSV Incremental Refresh

Summary

When fields in the source CSV file are renamed, especially primary key fields used for incremental refresh, best practices include running a detect source schema to ensure the stream continues to work correctly.


Question

Source Connector: Google Drive - CSV: Incremental Refresh:

4 of my fields got renamed in the source csv file I receive, 2 of them are used as primary key to detect changes and run the incremental refresh.

What shall I do in order to keep the stream working as it is suppose to? Is there any best practices?

E.g.
• shall I run a detect source schema?
• shall I do something else?
Best,
Kevin



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["google-drive-csv", "incremental-refresh", "renamed-fields", "primary-key", "detect-source-schema"]