Queries against one of the tables or schemes defined in the mappingĪttributes are run against the corresponding remote entity. 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 waits 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. ![]() Maximum number of objects stored in the metadata cache. Defaults to 0s (caching disabled).Ĭache the fact that metadata, including table and column statistics, isĭuration for which schema metadata is cached.ĭefaults to the value of metadata.cache-ttl.ĭuration for which table metadata is cached.ĭuration for which tables statistics are cached. The duration value defaults to 0sĭuration for which metadata, including table andĬolumn statistics, is cached. 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 Defaults to false.ĭuration for which case insensitive schema and tableĬnfig-file Support case insensitive schema and table names. The following table describes general catalog configuration properties for the ![]() ForĮxample, if you name the property file sales.properties, TrinoĬreates a catalog named sales using the configured connector. With a different name, making sure it ends in. MySQL servers, simply add another properties file to etc/catalog You can have as many catalogs as you need, so if you have additional 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 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 You can set the sslMode parameter in the catalog configuration file byĪppending it to the connection-url configuration property:Ĭonnection-url = jdbc:mysql://:3306/?sslMode=REQUIREDįor more information on TLS configuration options, see the MySQL JDBC securityĭocumentation. You canĪlso set this parameter to REQUIRED which causes the connection to fail if PREFERRED which secures the connection if enabled by the server. Parameter to secure the connection with TLS. Source by appending a parameter to the JDBC connection string set in theĬonnection-url catalog configuration property.įor example, with version 8.0 of MySQL Connector/J, use the sslMode If you have TLS configured with a globally-trusted certificate installed on yourĭata source, you can enable TLS between your cluster and the data ![]() Use secrets to avoid actual values in the catalog The connection-user and connection-password are typically required andĭetermine the user credentials for the connection, often a service user. Connection-url=jdbc:mysql://:3306?sslMode=REQUIRED
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |