-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Destinations still have "basic normalization" field in configuration #4710
Comments
No, I think @subodh1810 made a migration to remove these in the past |
This is weird, and may be I know whats going on, as part of this PR https://github.com/airbytehq/airbyte/pull/3624/files we deleted the here is the output of
As you can see above, am using dev image and there is no
which contains the basic_normalization attribute |
These are the following connectors that we need to publish
|
Oh we dont have to do snowflake cause Sherif already did it today, #4713 and in the new version
|
Redshift :
Dev :
|
Nice! Thanks for fixing it. |
Environment
Current Behavior
At configuration time at least 2 of our destinations still allow a user to configure basic normalization. I saw this in the most recent versions of Postgres and Snowflake. Didn't look past those, so there may be others.
Expected Behavior
The changes to connection settings that moved setting up normalization as part of a connection, means that a user should not be configuring this fields as part of the configurations for these destinations.
Steps to Reproduce
@ChristopheDuong is this a known issue? Is it an easy fix or is it going to be a headache because migrations?
The text was updated successfully, but these errors were encountered: