Closed mklaber closed 4 years ago
It would be good to simplify unit test logic a bit. As a hint - I would count number of 'TIMESTAMP_NTZ' literals in SQL to check that we are doing conversion for right number of columns.
It would be good to simplify unit test logic a bit. As a hint - I would count number of 'TIMESTAMP_NTZ' literals in SQL to check that we are doing conversion for right number of columns.
What happens if we accidentally start casting DATE
and stop casting TIMESTAMP
? Count doesn't change and the test would not detect that kind of failure. Explicit test cases are important here.
Following @czen88 's identification of a
CLIENT_TIMESTAMP_TYPE_MAPPING
edge case, this pull request addresses the case where a user may have setTIMESTAMP
to meanTIMESTAMP_TZ
viaCLIENT_TIMESTAMP_TYPE_MAPPING
.Additionally, following the existing HDFS → SF tests' pattern, this PR separates the
get_snowflake_to_hdfs_query
tests in to a query creation test and a column casting test.