You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we read tables from format("delta") and write the tables using the snowflake connector in format("snowflake"). The default behavior with previous versions of the connector (before RT 15.3ML) was identifiers named in capital letters in snowflake, same as would setting the option:
keep_column_case is = "off"
With 15.3 ML the tables saved in snowflake have lower cases and are double-quoted, as if the default behavior was
keep_column_case is = "on"
ex: "AccountId" VARCHAR(16777216),
by changing our options and setting the option explicitly : keep_column_case is = "off"
we recover the default behavior.
ex: ACCOUNTID VARCHAR(16777216),
From our point of view the default option value is not the one claimed in the documentation: it is not "off", but "on". So either there is a bug or the documentation needs to be updated.
Thanks for investigating,
The text was updated successfully, but these errors were encountered:
Using Databricks Runtime "15.3 ML (includes Apache Spark 3.5.0, Scala 2.12)" which packages
/databricks/jars/----ws_3_5--third_party--snowflake-jdbc--net.snowflake__snowflake-jdbc__shaded---414110472--net.snowflake__snowflake-jdbc__3.16.1.jar
we read tables from format("delta") and write the tables using the snowflake connector in format("snowflake"). The default behavior with previous versions of the connector (before RT 15.3ML) was identifiers named in capital letters in snowflake, same as would setting the option:
keep_column_case is = "off"
With 15.3 ML the tables saved in snowflake have lower cases and are double-quoted, as if the default behavior was
keep_column_case is = "on"
ex: "AccountId" VARCHAR(16777216),
by changing our options and setting the option explicitly : keep_column_case is = "off"
we recover the default behavior.
ex: ACCOUNTID VARCHAR(16777216),
From our point of view the default option value is not the one claimed in the documentation: it is not "off", but "on". So either there is a bug or the documentation needs to be updated.
Thanks for investigating,
The text was updated successfully, but these errors were encountered: