[
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284541#comment-16284541
]
ASF GitHub Bot commented on NIFI-4428:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2310
@joewitt There are presumably a handful of classes that the client needs
that are inexplicably associated with the server module. I will try to pare the
dependencies down to the minimum number. Also will add the reference in
nifi-nar-bundles.
Also, initial research indicates that there is no client security in Druid
at the time of this PR, so if there is nothing to do for Kerberos on the client
side, this PR (with updates from the previous comments and any other reviews)
should be good to go
> Implement PutDruid Processor and Controller
> -------------------------------------------
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
> Issue Type: New Feature
> Affects Versions: 1.3.0
> Reporter: Vadim Vaks
> Assignee: Matt Burgess
>
> Implement a PutDruid Processor and Controller using Tranquility API. This
> will enable Nifi to index contents of flow files in Druid. The implementation
> should also be able to handle late arriving data (event timestamp points to
> Druid indexing task that has closed, segment granularity and grace window
> period expired). Late arriving data is typically dropped. Nifi should allow
> late arriving data to be diverted to FAILED or DROPPED relationship. That
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing
> task can merge it into the correct segment in deep storage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
