You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2020/03/20 01:46:00 UTC

[jira] [Commented] (IOTDB-518) Apache IoTDB integration with MiNiFI/NiFi

    [ https://issues.apache.org/jira/browse/IOTDB-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063031#comment-17063031 ] 

Jialin Qiao commented on IOTDB-518:
-----------------------------------

Hi, [~le.nghia],

 

The English version of the system design is  this PR: [https://github.com/apache/incubator-iotdb/pull/910]

 

I would like to introduce the architecture in brief:

 

The tsfile module is a columnar file format for time series, it's similar with parquet, avro, orc file but more optimized for time series queries. It has independent file-level APIs.

The server module is the core engine of IoTDB, including the storage engine and query engine. The underlying data files are tsfiles. There are many clients can be used, such as Session, JDBC and other languages clients. They all derived from service-rpc module.

 

If your work is integrating IoTDB with other project. You may need to use the tsfile API, Session API (Native java api) or JDBC.  There is an example module in the root. It may help you :)

 

> Apache IoTDB integration with MiNiFI/NiFi
> -----------------------------------------
>
>                 Key: IOTDB-518
>                 URL: https://issues.apache.org/jira/browse/IOTDB-518
>             Project: Apache IoTDB
>          Issue Type: Wish
>          Components: Others
>            Reporter: Xiangdong Huang
>            Priority: Major
>              Labels: IoTDB, gsoc2020, mentor
>
> IoTDB is a database for storing time series data.
> MiNiFI is a data flow engine to transfer data from A to B, e.g., from PLC4X to IoTDB.
> This proposal is for integration IoTDB with MiNiFi.
>  * let MiNiFi/NiFi to support writing data into IoTDB.
>  
> Difficulty:  major
> mentors:



--
This message was sent by Atlassian Jira
(v8.3.4#803005)