Java Native API

Installation

Dependencies

• JDK >= 1.8
• Maven >= 3.6

How to install

In root directory:

mvn clean install -pl session -am -DskipTests

Using IoTDB Java Native API with Maven

<dependencies>
    <dependency>
      <groupId>org.apache.iotdb</groupId>
      <artifactId>iotdb-session</artifactId>
      <version>0.13.0-SNAPSHOT</version>
    </dependency>
</dependencies>

Syntax Description

• IoTDB-SQL interface: The input SQL parameter needs to conform to the syntax conventions and be escaped for JAVA strings. For example, you need to add a backslash before the double-quotes. (That is: after JAVA escaping, it is consistent with the SQL statement executed on the command line.)
• Other interfaces:
  • The node names in path or path prefix as parameter:
    • The node names which should be escaped by backticks (`) in the SQL statement, and escaping is not required here.
    • The node names enclosed in single or double quotes still need to be enclosed in single or double quotes and must be escaped for JAVA strings.
    • For the checkTimeseriesExists interface, since the IoTDB-SQL interface is called internally, the time-series pathname must be consistent with the SQL syntax conventions and be escaped for JAVA strings.
  • Identifiers (such as template names) as parameters: The identifiers which should be escaped by backticks (`) in the SQL statement, and escaping is not required here.

Native APIs

Here we show the commonly used interfaces and their parameters in the Native API:

Initialization

• Initialize a Session

// use default configuration 
session = new Session.Builder.build();
// initialize with a single node
session = 
    new Session.Builder()
        .host(String host)
        .port(int port)
        .build();
// initialize with multiple nodes
session = 
    new Session.Builder()
        .nodeUrls(List<String> nodeUrls)
        .build();
// other configurations
session = 
    new Session.Builder()
        .fetchSize(int fetchSize)
        .username(String username)
        .password(String password)
        .thriftDefaultBufferSize(int thriftDefaultBufferSize)
        .thriftMaxFrameSize(int thriftMaxFrameSize)
        .enableCacheLeader(boolean enableCacheLeader)
        .version(Version version)
        .build();

Version represents the SQL semantic version used by the client, which is used to be compatible with the SQL semantics of 0.12 when upgrading 0.13. The possible values are: V_0_12, V_0_13.

• Open a Session

void open()

• Open a session, with a parameter to specify whether to enable RPC compression

void open(boolean enableRPCCompression)

Notice: this RPC compression status of client must comply with that of IoTDB server

• Close a Session

void close()

Data Definition Interface (DDL Interface)

Storage Group Management

• Set storage group

void setStorageGroup(String storageGroupId)

• Delete one or several storage groups

void deleteStorageGroup(String storageGroup)
void deleteStorageGroups(List<String> storageGroups)

Timeseries Management

• Create one or multiple timeseries

void createTimeseries(String path, TSDataType dataType,
      TSEncoding encoding, CompressionType compressor, Map<String, String> props,
      Map<String, String> tags, Map<String, String> attributes, String measurementAlias)
void createMultiTimeseries(List<String> paths, List<TSDataType> dataTypes,
      List<TSEncoding> encodings, List<CompressionType> compressors,
      List<Map<String, String>> propsList, List<Map<String, String>> tagsList,
      List<Map<String, String>> attributesList, List<String> measurementAliasList)

• Create aligned timeseries

void createAlignedTimeseries(String prefixPath, List<String> measurements,
      List<TSDataType> dataTypes, List<TSEncoding> encodings,
      CompressionType compressor, List<String> measurementAliasList);

Attention: Alias of measurements are not supported currently.

• Delete one or several timeseries

void deleteTimeseries(String path)
void deleteTimeseries(List<String> paths)

• Check whether the specific timeseries exists.

boolean checkTimeseriesExists(String path)

Schema Template

Create a schema template for massive identical devices will help to improve memory performance. You can use Template, InternalNode and MeasurementNode to depict the structure of the template, and use belowed interface to create it inside session.

public void createSchemaTemplate(Template template);
Class Template {
    private String name;
    private boolean directShareTime;
    Map<String, Node> children;
    public Template(String name, boolean isShareTime);
    public void addToTemplate(Node node);
    public void deleteFromTemplate(String name);
    public void setShareTime(boolean shareTime);
}
Abstract Class Node {
    private String name;
    public void addChild(Node node);
    public void deleteChild(Node node);
}
Class MeasurementNode extends Node {
    TSDataType dataType;
    TSEncoding encoding;
    CompressionType compressor;
    public MeasurementNode(String name, 
                           TSDataType dataType, 
                           TSEncoding encoding,
                          CompressionType compressor);
}

We strongly suggest you implement templates only with flat-measurement (like object ‘flatTemplate’ in belowed snippet), since tree-structured template may not be a long-term supported feature in further version of IoTDB.

A snippet of using above Method and Class：

MeasurementNode nodeX = new MeasurementNode("x", TSDataType.FLOAT, TSEncoding.RLE, CompressionType.SNAPPY);
MeasurementNode nodeY = new MeasurementNode("y", TSDataType.FLOAT, TSEncoding.RLE, CompressionType.SNAPPY);
MeasurementNode nodeSpeed = new MeasurementNode("speed", TSDataType.DOUBLE, TSEncoding.GORILLA, CompressionType.SNAPPY);
// This is the template we suggest to implement
Template flatTemplate = new Template("flatTemplate");
template.addToTemplate(nodeX);
template.addToTemplate(nodeY);
template.addToTemplate(nodeSpeed);
createSchemaTemplate(flatTemplate);

After measurement template created, you can edit the template with belowed APIs.

**Attention: **

1. templates had been set could not be pruned

2. templates will be activated on one node by data points insertion of measurements within the template, or interface createTimeseriesOfSchemaTemplate

3. templates will not be shown by showtimeseries before activated

// Add aligned measurements to a template
public void addAlignedMeasurementsInTemplate(String templateName,
                              String[] measurementsPath,
                              TSDataType[] dataTypes,
                              TSEncoding[] encodings,
                              CompressionType[] compressors);
// Add one aligned measurement to a template
public void addAlignedMeasurementInTemplate(String templateName,
                                String measurementPath,
                                TSDataType dataType,
                                TSEncoding encoding,
                                CompressionType compressor);
// Add unaligned measurements to a template
public void addUnalignedMeasurementInTemplate(String templateName,
                                String measurementPath,
                                TSDataType dataType,
                                TSEncoding encoding,
                                CompressionType compressor);
// Add one unaligned measurement to a template
public void addUnalignedMeasurementsIntemplate(String templateName,
                                String[] measurementPaths,
                                TSDataType[] dataTypes,
                                TSEncoding[] encodings,
                                CompressionType[] compressors);
// Delete a node in template
public void deleteNodeInTemplate(String templateName, String path);

You can query measurement inside templates with these APIS:

// Return the amount of measurements inside a template
public int countMeasurementsInTemplate(String templateName);
// Return true if path points to a measurement, otherwise returne false
public boolean isMeasurementInTemplate(String templateName, String path);
// Return true if path exists in template, otherwise return false
public boolean isPathExistInTemplate(String templateName, String path);
// Return all measurements paths inside template
public List<String> showMeasurementsInTemplate(String templateName);
// Return all measurements paths under the designated patter inside template
public List<String> showMeasurementsInTemplate(String templateName, String pattern);

To implement schema template, you can set the template named templateName at path prefixPath.

Please notice that, we strongly recommend not setting templates on the nodes above the storage group to accommodate future updates and collaboration between modules.

void setSchemaTemplate(String templateName, String prefixPath);

Before setting template, you should first create the template using

void createSchemaTemplate(Template template);

After setting template to a certain path, you can query for info about template using belowed interface in session:

/** @return All template names. */
public List<String> showAllTemplates();
/** @return All paths have been set to designated template. */
public List<String> showPathsTemplateSetOn(String templateName);
/** @return All paths are using designated template. */
public List<String> showPathsTemplateUsingOn(String templateName)

If you are ready to get rid of schema template, you can drop it with belowed interface. Make sure the template to drop has been unset from MTree.

void unsetSchemaTemplate(String prefixPath, String templateName);
public void dropSchemaTemplate(String templateName);

Unset the measurement template named templateName from path prefixPath. When you issue this interface, you should assure that there is such a template set at the path.

If the template had been activated on one node, you should deactivate from it using the interface:

public void deactivateTemplateOn(String templateName, String prefixPath);

The passing in prefixPath is a literal path without wildcard(*or**), or a PathPattern to denote paths match the pattern.

The deactivation of the template will delete the data of the timeseries which is under the path of concatenation of path of the node and the measurements inside the activatede template.

Data Manipulation Interface (DML Interface)

Insert

It is recommended to use insertTablet to help improve write efficiency.

• Insert a Tablet，which is multiple rows of a device, each row has the same measurements
  • Better Write Performance
  • Support null values: fill the null value with any value, and then mark the null value via BitMap

void insertTablet(Tablet tablet)
public class Tablet {
  /** deviceId of this tablet */
  public String prefixPath;
  /** the list of measurement schemas for creating the tablet */
  private List<MeasurementSchema> schemas;
  /** timestamps in this tablet */
  public long[] timestamps;
  /** each object is a primitive type array, which represents values of one measurement */
  public Object[] values;
  /** each bitmap represents the existence of each value in the current column. */
  public BitMap[] bitMaps;
  /** the number of rows to include in this tablet */
  public int rowSize;
  /** the maximum number of rows for this tablet */
  private int maxRowNumber;
  /** whether this tablet store data of aligned timeseries or not */
  private boolean isAligned;
}

• Insert multiple Tablets

void insertTablets(Map<String, Tablet> tablet)

• Insert a Record, which contains multiple measurement value of a device at a timestamp. This method is equivalent to providing a common interface for multiple data types of values. Later, the value can be cast to the original type through TSDataType.

void insertRecord(String deviceId, long time, List<String> measurements,
   List<TSDataType> types, List<Object> values)

• Insert multiple Records

void insertRecords(List<String> deviceIds, List<Long> times,
    List<List<String>> measurementsList, List<List<TSDataType>> typesList,
    List<List<Object>> valuesList)

• Insert multiple Records that belong to the same device. With type info the server has no need to do type inference, which leads a better performance

void insertRecordsOfOneDevice(String deviceId, List<Long> times,
    List<List<String>> measurementsList, List<List<TSDataType>> typesList,
    List<List<Object>> valuesList)

Insert with type inference

When the data is of String type, we can use the following interface to perform type inference based on the value of the value itself. For example, if value is “true” , it can be automatically inferred to be a boolean type. If value is “3.2” , it can be automatically inferred as a flout type. Without type information, server has to do type inference, which may cost some time.

• Insert a Record, which contains multiple measurement value of a device at a timestamp

void insertRecord(String prefixPath, long time, List<String> measurements, List<String> values)

• Insert multiple Records

void insertRecords(List<String> deviceIds, List<Long> times, 
   List<List<String>> measurementsList, List<List<String>> valuesList)

• Insert multiple Records that belong to the same device.

void insertStringRecordsOfOneDevice(String deviceId, List<Long> times,
        List<List<String>> measurementsList, List<List<String>> valuesList)

Insert of Aligned Timeseries

The Insert of aligned timeseries uses interfaces like insertAlignedXXX, and others are similar to the above interfaces:

• insertAlignedRecord
• insertAlignedRecords
• insertAlignedRecordsOfOneDevice
• insertAlignedStringRecordsOfOneDevice
• insertAlignedTablet
• insertAlignedTablets

Delete

• Delete data before or equal to a timestamp of one or several timeseries

void deleteData(String path, long time)
void deleteData(List<String> paths, long time)

Query

• Raw data query. Time interval include startTime and exclude endTime

SessionDataSet executeRawDataQuery(List<String> paths, long startTime, long endTime)

• Query the last data, whose timestamp is greater than or equal LastTime

SessionDataSet executeLastDataQuery(List<String> paths, long LastTime)

IoTDB-SQL Interface

• Execute query statement

SessionDataSet executeQueryStatement(String sql)

• Execute non query statement

void executeNonQueryStatement(String sql)

Write Test Interface (to profile network cost)

These methods don’t insert data into database and server just return after accept the request.

• Test the network and client cost of insertRecord

void testInsertRecord(String deviceId, long time, List<String> measurements, List<String> values)
void testInsertRecord(String deviceId, long time, List<String> measurements,
        List<TSDataType> types, List<Object> values)

• Test the network and client cost of insertRecords

void testInsertRecords(List<String> deviceIds, List<Long> times,
        List<List<String>> measurementsList, List<List<String>> valuesList)
void testInsertRecords(List<String> deviceIds, List<Long> times,
        List<List<String>> measurementsList, List<List<TSDataType>> typesList
        List<List<Object>> valuesList)

• Test the network and client cost of insertTablet

void testInsertTablet(Tablet tablet)

• Test the network and client cost of insertTablets

void testInsertTablets(Map<String, Tablet> tablets)

Coding Examples

To get more information of the following interfaces, please view session/src/main/java/org/apache/iotdb/session/Session.java

The sample code of using these interfaces is in example/session/src/main/java/org/apache/iotdb/SessionExample.java，which provides an example of how to open an IoTDB session, execute a batch insertion.

For examples of aligned timeseries and measurement template, you can refer to example/session/src/main/java/org/apache/iotdb/AlignedTimeseriesSessionExample.java

Session Pool for Native API

We provide a connection pool (`SessionPool) for Native API. Using the interface, you need to define the pool size.

If you can not get a session connection in 60 seconds, there is a warning log but the program will hang.

If a session has finished an operation, it will be put back to the pool automatically. If a session connection is broken, the session will be removed automatically and the pool will try to create a new session and redo the operation. You can also specify an url list of multiple reachable nodes when creating a SessionPool, just as you would when creating a Session. To ensure high availability of clients in distributed cluster.

For query operations:

1. When using SessionPool to query data, the result set is SessionDataSetWrapper;
2. Given a SessionDataSetWrapper, if you have not scanned all the data in it and stop to use it, you have to call SessionPool.closeResultSet(wrapper) manually;
3. When you call hasNext() and next() of a SessionDataSetWrapper and there is an exception, then you have to call SessionPool.closeResultSet(wrapper) manually;
4. You can call getColumnNames() of SessionDataSetWrapper to get the column names of query result;

Examples: session/src/test/java/org/apache/iotdb/session/pool/SessionPoolTest.java

Or example/session/src/main/java/org/apache/iotdb/SessionPoolExample.java

Cluster information related APIs (only works in the cluster mode)

Cluster information related APIs allow users get the cluster info like where a storage group will be partitioned to, the status of each node in the cluster.

To use the APIs, add dependency in your pom file:

<dependencies>
    <dependency>
      <groupId>org.apache.iotdb</groupId>
      <artifactId>iotdb-thrift-cluster</artifactId>
      <version>0.13.0-SNAPSHOT</version>
    </dependency>
</dependencies>

How to open a connection:

import org.apache.thrift.protocol.TBinaryProtocol;
import org.apache.thrift.transport.TSocket;
import org.apache.thrift.transport.TTransport;
import org.apache.thrift.transport.TTransportException;
import org.apache.iotdb.rpc.RpcTransportFactory;
public class CluserInfoClient {
  TTransport transport;
  ClusterInfoService.Client client;
  public void connect() {
    transport =
            RpcTransportFactory.INSTANCE.getTransport(
                    new TSocket(
                            // the RPC address
                            IoTDBDescriptor.getInstance().getConfig().getRpcAddress(),
                            // the RPC port
                            ClusterDescriptor.getInstance().getConfig().getClusterRpcPort()));
    try {
      transport.open();
    } catch (TTransportException e) {
      Assert.fail(e.getMessage());
    }
    //get the client
    client = new ClusterInfoService.Client(new TBinaryProtocol(transport));
  }
  public void close() {
    transport.close();
  }
}

APIs in ClusterInfoService.Client:

• Get the physical hash ring of the cluster:

list<Node> getRing();

• Get data partition information of input path and time range:

/**
 * @param path input path (should contains a Storage group name as its prefix)
 * @return the data partition info. If the time range only covers one data partition, the the size
 * of the list is one.
 */
list<DataPartitionEntry> getDataPartition(1:string path, 2:long startTime, 3:long endTime);

• Get metadata partition information of input path:

/**
 * @param path input path (should contains a Storage group name as its prefix)
 * @return metadata partition information
 */
list<Node> getMetaPartition(1:string path);

• Get the status (alive or not) of all nodes:

/**
 * @return key: node, value: live or not
 */
map<Node, bool> getAllNodeStatus();

• get the raft group info (voteFor, term, etc..) of the connected node (Notice that this API is rarely used by users):

/**
 * @return A multi-line string with each line representing the total time consumption, invocation
 *     number, and average time consumption.
 */
string getInstrumentingInfo();