The following example sets a simple comment that identifies each query sent by Variables from the Trino cluster with the comment, use the Information is available in the logs of the datasource. The comment can provide more context about the query. $TRACE_TOKEN: The trace token configured with the client tool. $SOURCE: The identifier of the client tool used to submit the query, for $USER: The name of the user who submits the query to Trino. The format of thisĬomment can contain any characters and the following metadata: The optional parameter ment-format allows you to configure a SQLĬomment that is sent to the datasource with each query. However, it can also increase latency for some queries. Using a large timeout can potentially result in more detailedĭynamic filters. Maximum duration for which Trino will wait for dynamicįilters to be collected from the build side of joins before starting a Push down dynamic filters into JDBC queries Maximum number of statements in a batched execution.ĭo not change this setting from the default. Maximum number of objects stored in the metadata cache The duration for which metadata, includingĬache the fact that metadata, including table and column statistics, is Trino to disambiguate between schemas and tables with similar names inĬ-periodįrequency with which Trino checks the name matching configuration fileįor changes. Path to a name mapping configuration file in JSON format that allows Support case insensitive schema and table names.Ĭnfig-file The following table describes general catalog configuration properties for the If you name the property file sales.properties, Trino creates aĬatalog named sales using the configured connector. With a different name, making sure it ends in. To add another catalog, simply add another properties file to etc/catalog Multiple instances of the Redshift connector. Or want to connect to multiple Redshift clusters, you must configure Thus, if you have multiple Redshift databases, The Redshift connector can only access a single database withinĪ Redshift cluster. Multiple Redshift databases or clusters # Password for the password key store entity. Name of the key store entity to use as the password. Password for the user name key store entity. Name of the key store entity to use as the user name. The location of the Java Keystore file, from which to read credentials.įile format of the keystore file, for example JKS or PEM. It mustĬontain the connection-user and connection-password properties. Location of the properties file where credentials are present. Name of the extra credentials property, whose value to use as the See extraCredentials in Parameter reference. Name of the extra credentials property, whose value to use as the user The following table describes configuration properties You can use secrets to avoid storing sensitive Inline, in the connector configuration fileĪs extra credentials set when connecting to Trino The connector can provide credentials for the data source connection Multiple Redshift databases or clustersĬonnection-url = jdbc:redshift://:5439/database SSL=TRUE įor more information on TLS configuration options, see the Redshift JDBC driverĭocumentation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |