HANA Connector¶

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.

Configuration¶

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:

connector.name=hana
connection-url=jdbc:sap://[serverName[\instanceName][:portNumber]]
connection-user=root
connection-password=secret

Connection security¶

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:

connection-url=jdbc:sap://<host>:<port>?encrypt=true;

Other SSL configuration properties that can be configured using the connection-url:

SSL Configuration Properties¶

A connection string using a truststore would be similar to the following example:

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.

General Configuration Properties¶

Procedures¶

Use the CALL statement to perform data manipulation or administrative tasks. Procedures are available in the system schema of the catalog.

Execute Procedure¶

Underlying datasources may support some operation or SQL syntax which is not supported by Presto, either at the parser level or at the connector level. Trying to run such SQL statements in Presto can result in errors during parsing or analysing. For example, SAP Hana supports creating auto generated primary keys which is not supported in Presto. Running this procedure enables users to do a SQL passthrough to the underlying database, and Presto just acts as a middle man for passing the statement.

The following arguments are available:

Examples:

• Create a table with auto generated primary key:

  CALL hana.system.execute('create table schema1.table1 (id BIGINT NOT NULL GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY, a int)')
  
  CALL hana.system.execute(QUERY => 'create table schema1.table1 (id BIGINT NOT NULL GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY, a int)')
  

Querying HANA¶

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.

HANA Connector Limitations¶

The following SQL statements are not supported:

• DELETE

• GRANT

• REVOKE

• SHOW GRANTS

• SHOW ROLES

• SHOW ROLE GRANTS