7.22. Thrift Connector

In order to use the Thrift connector with an external system, you need to implement the interface, found below. Next, you configure the Thrift connector to point to a set of machines, called Thrift servers, that implement the interface. As part of the interface implementation, the Thrift servers will provide metadata, splits and data. The connector will randomly choose a server to talk to from the available instances for metadata calls, or for data calls unless the splits include a list of addresses. All requests are assumed to be idempotent and can be retried freely among any server.

To configure the Thrift connector, create a catalog properties file etc/catalog/thrift.properties with the following content, replacing the properties as appropriate:

You can have as many catalogs as you need, so if you have additional Thrift systems to connect to, simply add another properties file to etc/catalog with a different name (making sure it ends in .properties).

Comma-separated list of thrift servers in the form of host:port. For example:

This property is required; there is no default.

Maximum size of a data response that the connector accepts. This value is sent by the connector to the Thrift server when requesting data, allowing it to size the response appropriately.

Number of refresh threads for metadata cache.

This property is optional; the default is 1.

The following IDL describes the that must be implemented: