You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2018/09/21 17:59:00 UTC

[jira] [Commented] (NIFI-5624) Improve stability of EncryptedWriteAheadProvenanceRepositoryTest

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

Andy LoPresto commented on NIFI-5624:
-------------------------------------

Hi [~markap14], I believe you'll be better suited to fix this, as I don't recall the EWAPR doing any disk interaction. It simply intercepts the data being serialized/deserialized and encrypts/decrypts it, and then delegates the file read/write to WAPR. Thanks. 

> Improve stability of EncryptedWriteAheadProvenanceRepositoryTest
> ----------------------------------------------------------------
>
>                 Key: NIFI-5624
>                 URL: https://issues.apache.org/jira/browse/NIFI-5624
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Tools and Build
>    Affects Versions: 1.7.1
>            Reporter: Joseph Witt
>            Assignee: Andy LoPresto
>            Priority: Major
>
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.164 s <<< FAILURE! - in org.apache.nifi.provenance.EncryptedWriteAheadProvenanceRepositoryTest
> testShouldRegisterAndGetEvent(org.apache.nifi.provenance.EncryptedWriteAheadProvenanceRepositoryTest)  Time elapsed: 0.021 s  <<< ERROR!
> java.io.FileNotFoundException: Cannot create TOC Reader because the file target/storage/cbb4db1c-9cee-43e5-907f-8137a8178197/toc/0.toc does not exist
> 	at org.apache.nifi.provenance.EncryptedWriteAheadProvenanceRepositoryTest.testShouldRegisterAndGetEvent(EncryptedWriteAheadProvenanceRepositoryTest.groovy:277)
> Wasn't sure if this was better to flag for [~alopresto] or [~markap14] so just a heads up.  In NIFI-4806 i'm going to ignore it for now and this JIRA will be to improve it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)