Destination Databricks: connector should support schema evolution (schemaMerge) #26658
Labels
area/connectors
Connector related issues
community
connectors/destination/databricks
connectors/destinations-warehouse
releaseStage/alpha
team/destinations
Destinations team's backlog
type/enhancement
New feature or request
What area the feature impact?
Connectors
Revelant Information
Databricks and its delta tables support schema evolution via the
COPY INTO
command parameter'smergeSchema=true
. The connector should provide a parameter to enable or disable schema evolution.In #26942, we added an option in the connector configuration interface to enable or disable schema evolution:
![image](https://private-user-images.githubusercontent.com/16660/241216292-3995bd84-f82f-43fd-b305-a43b2ec5c166.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1Nzc1MTQsIm5iZiI6MTczOTU3NzIxNCwicGF0aCI6Ii8xNjY2MC8yNDEyMTYyOTItMzk5NWJkODQtZjgyZi00M2ZkLWIzMDUtYTQzYjJlYzVjMTY2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDIzNTMzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWFiODQyODVlOGYyMGE2YjFmNDRhN2I1YTE1MzAxNjIzOTY2NDc4NGI5MmYxY2NlZjg0NmVjN2NiNmI2NGYwNGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ssanrU8zaEFvnj4Ty82eZ6AtFvuSwWMFp-Wjzy7hykU)
This option, once enabled, sets the following parameter to the COPY INTO statement used to load the data into the destination table (set to
false
by default):COPY_OPTIONS ('mergeSchema' = 'true')
We conducted some tests locally and it works great so far. We planned on running it in production in the coming weeks.
The text was updated successfully, but these errors were encountered: