[
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286317#comment-16286317
]
ASF GitHub Bot commented on NIFI-4428:
--------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/2310
Hey @mattyb149, I didn't have time to look into yet but I saw the release
of [Druid 0.11](http://druid.io/blog/2017/12/04/druid-0-11-0.html) with TLS
support. I don't know if this could be related to the PR but wanted to mention
it in case it can be added.
> 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)
