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

Xiangdong Huang commented on IOTDB-518:
---------------------------------------

Hi  [~le.nghia],

Welcome! 

As for the GSoc process, I am also new to that. Normally, You need to submit a 
proposal for your plan and design, then we make a discussion about your 
proposal and then work together.

[~njiang] is more experienced.

 

Now let's turn to the project...

As far as I know, MiniFi is a  dataflow  management tool. But I have little 
knowledge about the Concepts in MiniFi, like FlowFile, Processor, Connection 
etc..

IMO, I think we can develop some processors in MiniFi to support IoTDB:

1.  MiniFi reads a batch of data from IoTDB (or a TsFile)  and forwards te data 
to analysis systems (e.g., Flink, Spark.) 

2. MiniFi forwards a batch of data or a record of data to IoTDB (a TsFile) to 
let IoTDB persist the data.

To do that, you need to know IoTDB's API (session API, and IoTDB SQL), and 
TsFile API (for read and write operations) 

 

Christefor Dutz said PLC4X has integrated with MiniFI. As PLC4X is definitely  
a kind data source to IoTDB. I think the integration between them may help us 
to understand what we can do next.

 

 

 

 

> 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)

Reply via email to