nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-748) If unable to find a specific Provenance event, should not fail entire search
Date Sun, 15 Nov 2015 15:48:10 GMT


ASF GitHub Bot commented on NIFI-748:

Github user trkurc commented on a diff in the pull request:
    --- Diff: nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/lucene/
    @@ -47,9 +46,6 @@
     public class DocsReader {
         private final Logger logger = LoggerFactory.getLogger(DocsReader.class);
    -    public DocsReader(final List<File> storageDirectories) {
    -    }
    --- End diff --
    100% agree. Other projects use annotations to warn folks of risk when using public methods
that aren't extension points (e.g. @PublicForTests or @Experimental), but I'd settle for a

> If unable to find a specific Provenance event, should not fail entire search
> ----------------------------------------------------------------------------
>                 Key: NIFI-748
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Oleg Zhurakousky
>             Fix For: 0.4.0
> We have a case where running with the prov being written to a disk that can be ejected.
Disk was accidentally ejected while running. Provenance Event appears to have been indexed
but event is not in the repo.
> Specifically, we are reaching Line 104 of DocsReader:
> {code}
> throw new IOException("Failed to find Provenance Event " + d);
> {code}
> As a result, searching for a specific Component ID is returning an error, so we can't
search on that Component ID at all (unless we shrink the time range to a time when that didn't
> We should generate a warning, and notify the user that X number of events could not be
found and show what we can, rather than erroring out entirely.

This message was sent by Atlassian JIRA

View raw message