presto-docs/src/main/sphinx/connector/hana.rst
The HANA connector allows querying and creating tables in an external HANA database. This can be used to join data between different systems like HANA and Hive, or between two different HANA instances.
To configure the HANA connector, create a catalog properties file
in etc/catalog named, for example, hana.properties, to
mount the HANA connector as the hana catalog.
Create the file with the following contents, replacing the connection properties as appropriate for your setup:
.. code-block:: none
connector.name=hana
connection-url=jdbc:sap://[serverName[\instanceName][:portNumber]]
connection-user=root
connection-password=secret
The JDBC driver and connector automatically use Transport Layer Security (TLS) encryption and certificate validation. This requires a suitable TLS certificate configured on your Hana database host.
To enable encryption in the connection string, use the encrypt property:
.. code-block:: none
connection-url=jdbc:sap://<host>:<port>?encrypt=true;
Other SSL configuration properties that can be configured using the connection-url:
SSL Configuration Properties
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
================================================== ==================================================================== ===========
Property Name Description Default
================================================== ==================================================================== ===========
validateCertificate Indicates that the SSL certificate presented by the server true
should be validated against the truststore specified.
trustStoreType File format of the truststore file, for example JKS.
trustStore The path to the truststore file.
trustStorePassword The password for the truststore.
================================================== ==================================================================== ===========
A connection string using a truststore would be similar to the following example:
.. code-block:: none
connection-url=jdbc:sap://<host>:<port>?encrypt=true&validateCertificate=true&trustStore=path/to/truststore.jks&trustStorePassword=password&trustStoreType=jks
Multiple HANA Databases or Servers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The HANA connector can only access a single database within a HANA server. If you have multiple HANA databases, or want to connect to multiple HANA instances, you must configure multiple catalogs, one for each instance.
To add another catalog, add another properties file to etc/catalog
with a different name (making sure it ends in .properties). For example,
if you name the property file sales.properties, Presto will create a
catalog named sales using the configured connector.
================================================== ==================================================================== ===========
Property Name Description Default
================================================== ==================================================================== ===========
user-credential-name Name of the extraCredentials property whose value is the JDBC
driver's user name. See extraCredentials in
:ref:Parameter Reference <jdbc-parameter-reference>.
password-credential-name Name of the extraCredentials property whose value is the JDBC
driver's user password. See extraCredentials in
:ref:Parameter Reference <jdbc-parameter-reference>.
case-insensitive-name-matching Match dataset and table names case-insensitively. false
case-insensitive-name-matching.cache-ttl Duration for which remote dataset and table names will be
cached. Set to 0ms to disable the cache. 1m
list-schemas-ignored-schemas List of schemas to ignore when listing schemas. information_schema
case-sensitive-name-matching Enable case sensitive identifier support for schema and table false
names for the connector. When disabled, names are matched
case-insensitively using lowercase normalization.
================================================== ==================================================================== ===========
The HANA connector provides access to all schemas visible to the specified user in the configured database.
For the following examples, assume the HANA catalog is hana.
You can see the available schemas by running SHOW SCHEMAS::
SHOW SCHEMAS FROM hana;
If you have a schema named web, you can view the tables
in this schema by running SHOW TABLES::
SHOW TABLES FROM hana.web;
You can see a list of the columns in the clicks table in the web database
using either of the following::
DESCRIBE hana.web.clicks;
SHOW COLUMNS FROM hana.web.clicks;
Finally, you can query the clicks table in the web schema::
SELECT * FROM hana.web.clicks;
If you used a different name for your catalog properties file, use
that catalog name instead of hana in the above examples.
The following SQL statements are not supported:
/sql/delete/sql/grant/sql/revoke/sql/show-grants/sql/show-roles/sql/show-role-grants