TheĮxample accesses the column name from the first value in each tuple. The following example uses the description attribute to retrieve the list of column names after executing a query. The following examples demostrate how to access the metadata from the returned tuples and ResultMetadata objects.Įxample: Getting the column name metadata by index (versions 2.4.5 and earlier): You canĪccess the metadata by index or, in 2.4.6 and later versions, by (TheĮach tuple and ResultMetadata object contains the metadata for a column (the column name, data type, etc.). Version 2.4.6 and later: A list of ResultMetadata objects.

Version 2.4.5 and earlier: A list of tuples. The description attribute is set to one of the following values: The describe method is available in the Snowflake Connector for Python 2.4.6 and more recent versions. To access the metadata without having to execute the query, call the describe() method. To access the metadata after calling the execute() method to execute the query, use the description To retrieve metadata about each column in the result set (e.g. If none of the cache layers contain the OCSP response, the client attempts to fetch the validation status directly from the CA’s OCSP server. As long as the cache is valid, the connector can still validate the certificate revocation status. in the event the actual OCSP server is down). ~/.cache/snowflake) is purged.Ĭaching also addresses availability issues for OCSP servers (i.e. Memory cache, which persists for the life of the process.įile cache, which persists until the cache directory (e.g. In addition to the regular HTTPS protocol, the connector also checks the TLS/SSL certificate revocation status on each connection via OCSP (Online Certificate Status Protocol) and aborts the connection if it finds the certificate is revoked or the OCSP status is not reliable.īecause each Snowflake connection triggers up to three round trips with the OCSP server, multiple levels of cache for OCSP responses have been introduced to reduce the network overhead added to the connection: Amazon S3 for staging data files and Okta for federated authentication). To ensure all communications are secure, the Snowflake Connector for Python uses the HTTPS protocol to connect to Snowflake, as well as to connect to all other services (e.g. If more than one value is specified, values should be separated by commas, for example: The end of a hostname (or a complete hostname), for example: Each value specified should be one of the following: For example, access to Amazon S3 can bypass the proxy server by specifying NO_PROXY='.'. Optionally NO_PROXY can be used to bypass the proxy for specific communications. If you must use your SSL proxy, we strongly recommend that you update the server policy to pass through the Snowflake certificate such that no certificate is altered in the middle of Your proxy server must use a publicly-available Certificate Authority (CA), reducing potential security risks such as a MITM (Man In The Middle) attack through a compromised proxy. Snowflake’s security model does not allow Secure Sockets Layer (SSL) proxies (using an HTTPS certificate).

Low time multi engine pilot jobs