[ https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327530#comment-16327530 ]
ASF subversion and git services commented on NIFI-4428: ------------------------------------------------------- Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch refs/heads/master from [~ca9mbu] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ] NIFI-4428: Replaced JSON input with RecordReader using per-record flowfiles NIFI-4428: Added initial L&N, fixed dependency hierarchy NIFI-4428: Exposed additional ZK properties NIFI-4428: More work to reduce dependencies in Druid artifacts NIFI-4428: Removed inaccessible attribute NIFI-4428: Fixed typo in property description NIFI-4428: Updates to Druid NAR L&N NIFI-4428: Updated LICENSE to refer to ICU License for icu4j > 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 > Priority: Major > > 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 (v7.6.3#76005)