Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data.
Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.
Apache NiFi includes the following capabilities:
This is a processor that reads the content of the incoming FlowFile as individual records using the configured ‘Record Reader’ and writes them to Apache IoTDB using native interface.
| property | description | default value | necessary |
|---|---|---|---|
| Host | The host of IoTDB. | null | true |
| Port | The port of IoTDB. | 6667 | true |
| Username | Username to access the IoTDB. | null | true |
| Password | Password to access the IoTDB. | null | true |
| Prefix | The Prefix begin with root. that will be add to the tsName in data. It can be updated by expression language. | null | true |
| Time | The name of time field | null | true |
| Record Reader | Specifies the type of Record Reader controller service to use for parsing the incoming data and determining the schema. | null | true |
| Schema | The schema that IoTDB needs doesn‘t support good by NiFi. Therefore, you can define the schema here. Besides, you can set encoding type and compression type by this method. If you don’t set this property, the inferred schema will be used. It can be updated by expression language. | null | false |
| Aligned | Whether using aligned interface? It can be updated by expression language. | false | false |
| MaxRowNumber | Specifies the max row number of each tablet. It can be updated by expression language. | 1024 | false |
There are a couple of rules about flowfile:
Record Reader.STRING or LONG.root..INT, LONG, FLOAT, DOUBLE, BOOLEAN, TEXT.As mentioned above, converting schema by property which is more flexible and stronger than inferred schema.
The structure of property Schema:
{ "fields": [{ "tsName": "s1", "dataType": "INT32", "encoding": "RLE", "compressionType": "GZIP" }, { "tsName": "s2", "dataType": "INT64", "encoding": "RLE", "compressionType": "GZIP" }] }
Note
Time. The rest must be arranged in the same order as in field of JSON.timeType and fields.LONG and STRING for timeType.tsName and dataType must be set.Prefix will be added to tsName as the field name when add data to IoTDB.dataTypes are INT32, INT64, FLOAT, DOUBLE, BOOLEAN, TEXT.encoding are PLAIN, DICTIONARY, RLE, DIFF, TS_2DIFF, BITMAP, GORILLA_V1, REGULAR, GORILLA, CHIMP, SPRINTZ, RLBE.compressionType are UNCOMPRESSED, SNAPPY, GZIP, LZO, SDT, PAA, PLA, LZ4, ZSTD, LZMA2.| relationship | description |
|---|---|
| success | Data can be written correctly or flow file is empty. |
| failure | The shema or flow file is abnormal. |
This is a processor that reads the sql query from the incoming FlowFile and using it to query the result from IoTDB using native interface. Then it use the configured ‘Record Writer’ to generate the flowfile
| property | description | default value | necessary |
|---|---|---|---|
| Host | The host of IoTDB. | null | true |
| Port | The port of IoTDB. | 6667 | true |
| Username | Username to access the IoTDB. | null | true |
| Password | Password to access the IoTDB. | null | true |
| Record Writer | Specifies the Controller Service to use for writing results to a FlowFile. The Record Writer may use Inherit Schema to emulate the inferred schema behavior, i.e. An explicit schema need not be defined in the writer, and will be supplied by the same logic used to infer the schema from the column types. | null | true |
| iotdb-query | The IoTDB query to execute. Note: If there are incoming connections, then the query is created from incoming FlowFile's content otherwise"it is created from this property. | null | false |
| iotdb-query-chunk-size | Chunking can be used to return results in a stream of smaller batches (each has a partial results up to a chunk size) rather than as a single response. Chunking queries can return an unlimited number of rows. Note: Chunking is enable when result chunk size is greater than 0 | 0 | false |
| relationship | description |
|---|---|
| success | Data can be written correctly or flow file is empty. |
| failure | The shema or flow file is abnormal. |