Skip to content

Upgrading destination-snowflake to Destinations V2 loses case insensitivity with no warning or ability to preserve case insensitivity, breaking all query paths. #30139

Closed
@rtol5

Description

@rtol5

Connector Name

destination-snowflake

Connector Version

3.0.1

Airbyte Version

0.50.24

What step the error happened?

Updating the connector

Revelant information

We upgraded destination-snowflake to Destinations V2 by following this guide. Everything appeared to work correctly, until we noticed that all tables and schemas (edit: column names too) for sources with lowercase names now show up in separate lowercase schemas/tables.

This isn't called out anywhere in the upgrade guide linked above, and Airbyte's UI doesn't appear to allow users to rename table names (only schemas). Most importantly, there doesn't seem to be a way to have Airbyte retain case-insensitivity to prevent this problem.

This is quite a major breaking change that causes every existing system or human query to break. Can the ability to retain case insensitivity be added for destination-snowflake? I'd even say that this feature should be table stakes for Destinations V2 given the ramifications.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions