Exam4Training

Which class in the snowflake.connector.converter_null module do you use for this feature?

In order to improve query perfromance, you can bypass data conversions from the Snowflake internal data type to the native Python data type.

Which class in the snowflake.connector.converter_null module do you use for this feature?
A . SnowflakeNoConverterToPython
B. PythonNoConverterToSnowflake
C. ByPassDataConversion

Answer: A

Explanation

https://docs.snowflake.com/en/user-guide/python-connector-example.html#improving-query-performance-by-bypassing-data-conversion

To improve query performance, use the SnowflakeNoConverterToPython class in the snowflake.connector.converter_null module to bypass data conversions from the Snowflake internal data type to the native Python data type, e.g.:

from snowflake.connector.converter_null import SnowflakeNoConverterToPythoncon = snowflake.connector.connect(



converter_class=SnowflakeNoConverterToPython

)

for rec in con.cursor().execute("SELECT * FROM large_table"):

# rec includes raw Snowflake data

As a result, all data is represented in string form such that the application is responsible for converting it to the native Python data types. For example, TIMESTAMP_NTZ and TIMESTAMP_LTZ data are the epoch time represented in string form, and TIMESTAMP_TZ data is the epoch time followed by a space followed by the offset to UTC in minutes represented in string form.

No impact is made to binding data; Python native data can still be bound for updates.

Latest DEA-C01 Dumps Valid Version with 100 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Exit mobile version