[
https://issues.apache.org/jira/browse/NIFI-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993325#comment-15993325
]
ASF GitHub Bot commented on NIFI-3594:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1686
I rebased and resolved the conflict. There were test errors in
`nifi-gcp-processors` and `nifi-poi-processors` where
`MockComponentLog#getErrorMessages()` was returning twice the number of
expected errors. With @bbende , we determined this was because
`src/test/resources/logback-test.xml` in `nifi-data-provenance-utils` set the
log level to `DEBUG`, and `MockComponentLog` double records the error message
if `DEBUG` is enabled. I provided custom `src/test/resources/logback-test.xml`
files in the two offending modules to ensure that the log level is set as
expected when those tests run.
Merged.
> Implement encrypted provenance repository
> -----------------------------------------
>
> Key: NIFI-3594
> URL: https://issues.apache.org/jira/browse/NIFI-3594
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Affects Versions: 1.1.1
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Labels: encryption, provenance, repository
> Fix For: 1.2.0
>
>
> I am going to start with the provenance repository, as the new implementation
> of {{WriteAheadProvenanceRepository}} has the most recent design decisions
> and has not been available in a released version yet, so there should be
> minimal backward compatibility concerns.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
