You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/18 21:28:20 UTC

[jira] [Commented] (NIFI-2600) Provenance Repository can close Index Reader too soon

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

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

GitHub user markap14 opened a pull request:

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

    NIFI-2600: Ensure that we do not close Index Searchers prematurely, e…

    …ven if they are poisoned

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

    $ git pull https://github.com/markap14/nifi NIFI-2600

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

    https://github.com/apache/nifi/pull/896.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 #896
    
----
commit 3b4ce678624235d7824caec9ae5dd2c8745f7175
Author: Mark Payne <ma...@hotmail.com>
Date:   2016-08-18T19:29:34Z

    NIFI-2600: Ensure that we do not close Index Searchers prematurely, even if they are poisoned

----


> Provenance Repository can close Index Reader too soon
> -----------------------------------------------------
>
>                 Key: NIFI-2600
>                 URL: https://issues.apache.org/jira/browse/NIFI-2600
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 1.0.0
>
>
> In NIFI-2452, we addressed an issue where the Persistent Provenance Repo closed Index Readers / Index Searchers before they should. I have found another case in which that can happen.
> Using a separate JIRA rather than re-opening the other, since NIFI-2452 has a fix Version of both 1.0.0-BETA and 1.0.0 and 1.0.0-BETA has already been released.



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