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

ASF GitHub Bot commented on MINIFI-23:
--------------------------------------

GitHub user apiri opened a pull request:

    https://github.com/apache/nifi-minifi/pull/18

    MINIFI-23 Removing indexing from provenance repository

    Providing base implementation of a non-indexed, persistent, provenance 
repository using NiFi interfaces and package structure.
    
    Had initially started extracting out the API, but altered approach to have 
this implementation work out of the NiFi package structure to avoid method 
scoping issues.  The prior efforts were kept on a branch locally and will aid 
in the efforts of MINIFI-29.
    
    Some TODOs and notes are left behind to adjust implementation once the new 
FlowController and associated API are accomplished.

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

    $ git pull https://github.com/apiri/nifi-minifi MINIFI-23

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

    https://github.com/apache/nifi-minifi/pull/18.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 #18
    
----
commit 83a8d8796329b68344397369a86adf8c4ef99d5d
Author: Aldrin Piri <[email protected]>
Date:   2016-04-21T15:27:06Z

    MINIFI-23 Providing base implementation of a non-indexed, persistent
    provenance repository using NiFi interfaces and package structure.

----


> Remove provenance indexing
> --------------------------
>
>                 Key: MINIFI-23
>                 URL: https://issues.apache.org/jira/browse/MINIFI-23
>             Project: Apache NiFi MiNiFi
>          Issue Type: Sub-task
>            Reporter: Aldrin Piri
>            Assignee: Aldrin Piri
>
> As these items are not being searched on the agent, the associated 
> functionality is unneeded.  These classes should be refactored/rewritten as 
> needed to cover the use cases being addressed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to