[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274749#comment-16274749 ] 

ASF GitHub Bot commented on NIFI-4428:
--------------------------------------

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/2310

    NIFI-4428: Add PutDruidRecord processor and DruidTranquilityController service

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi NIFI-4428

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2310.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2310
    
----
commit e502364ffb18683747c93af1deb85b0185b165a6
Author: vvaks <vv...@hortonworks.com>
Date:   2017-09-27T17:23:23Z

    NIFI-4428: - Implement PutDruid Processor and Controller
    
    update
    
    added provenance report
    
    added parameters for batch control
    
    WIP

commit d7db6ed526a8e2a06625a2a0cd1e46ea2b923ff3
Author: Matthew Burgess <ma...@apache.org>
Date:   2017-11-22T16:36:30Z

    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

----


> 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
>
> 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)