I am using snowflake destination connector version number v3.9.1, earlier i was using v0.4.48, In the older version i was able to get the raw table names as _AIRBYTE_RAW_TABLE_NAME but now i am getting it in a wierd format which is multicase table is getting created for SCHEMA_NAME_raw___stream_table_name. The problem is it creates a multicase table on the snowflake

Based on the information provided in the knowledge sources, I can explain the change you're experiencing with the Snowflake destination connector. The behavior you're describing is related to a change introduced in Destinations V2, which was implemented in version 3.0.0 of the Snowflake destination connector. This change affects how table names are handled in Snowflake. In the older version (0.4.48), raw tables were created with names like

_AIRBYTE_RAW_TABLE_NAME

, as you mentioned. However, in the newer versions (including 3.9.1 that you're currently using), there have been changes to how table names are handled. According to the [Snowflake Destination Changelog](https://docs.airbyte.com/integrations/destinations/snowflake#changelog), version 3.1.0 introduced a change to "Upcase final table names to allow case-insensitive references". This change was made to improve consistency and ease of use when referencing tables in Snowflake. The mixed case table names you're seeing (like

SCHEMA_NAME_raw___stream_table_name

) are likely a result of these changes. Snowflake itself is case-insensitive for unquoted identifiers, but it preserves the case when identifiers are quoted. To address your concern about the "weird format" and mixed case tables, you should be aware that this is the intended behavior in the newer versions of the connector. The raw tables are now created with a different naming convention, and the final tables are explicitly uppercased. If this change is causing issues with your existing workflows or queries, you may need to update your SQL queries or downstream processes to account for the new naming convention. For more detailed information on the changes introduced in Destinations V2 and how they affect Snowflake, you can refer to the [Destinations V2 Implementation Differences](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#destinations-v2-implementation-differences) documentation. If you need to revert to the old behavior, you would need to downgrade to a version prior to 3.0.0. However, this is not recommended as you would miss out on important updates and improvements. Instead, it's better to adapt your processes to work with the new naming convention.