[ https://issues.apache.org/jira/browse/NIFI-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994972#comment-14994972 ]
Joseph Witt commented on NIFI-748: ---------------------------------- given the lack of action on this we should move it off 040. But given the trivial nature of the fix and its implications of not being fixed I am inclined that we just knock this out. > If unable to find a specific Provenance event, should not fail entire search > ---------------------------------------------------------------------------- > > Key: NIFI-748 > URL: https://issues.apache.org/jira/browse/NIFI-748 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework > Reporter: Mark Payne > 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 occur). > 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 (v6.3.4#6332)