[
https://issues.apache.org/jira/browse/NIFI-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571028#comment-17571028
]
David Handermann commented on NIFI-10234:
-----------------------------------------
Thanks for the reply [~xuanronaldo].
Based on your example, what I was suggesting is that instead of requiring a
field named {{Time}}, the Record processing approach would read the record, and
then use a field based on a configuration property. For example, instead of
requiring a specific name, the IoTDB {{Time}} field could be mapped from
another input Record field. For example:
{noformat}
Created,root.sg.d1.s1,root.sg.d1.s2
1658763997000,1,1
1658763998000,2,2
{noformat}
In that scenario, the Time Record Field would be configured with a value of
{{Created}}. If this approach makes sense, it would avoid having to convert
record fields prior to sending records to {{PutIoTDB}}.
> implement a processor of Apache IoTDB
> -------------------------------------
>
> Key: NIFI-10234
> URL: https://issues.apache.org/jira/browse/NIFI-10234
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Xuan Ronaldo
> Priority: Major
>
> Hi, folks
>
> I'm a contributer of Apache IoTDB. Recently, I have implemented a processor
> which can write data to IoTDB. I'd like to submit it to the NiFi as a
> build-in processor. Besides, there are more processors or controller services
> will be developed.
>
> Regards,
> Xuan Ronaldo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
