[
https://issues.apache.org/jira/browse/NIFI-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989449#comment-15989449
]
ASF GitHub Bot commented on NIFI-3594:
--------------------------------------
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/1686
@alopresto Ran a test where I had an existing unencrypted provenance repo
and switched to the encrypted provider. The issues [you've
documented](https://github.com/alopresto/nifi/blob/276f31aa85d9ec401fb34f939238c6646e187ae6/nifi-docs/src/main/asciidoc/user-guide.adoc#potential-issues)
did occur (where switching between configuration would lead to errors in the
log and when querying). However I'm wondering two things:
1) Can there be a friendlier error message in the logs for those errors? I
saw lots of errors around ClassCastException between the old and new Record
Readers. Just wondering if NiFi could simply say detected a mismatch and that
it could be due to a change in repo providers?
2) I also saw the UI error (see below), however I expected to eventually be
able to retrieve the events that were subject to encryption. I have a super
short and small flow that runs every 10s. Perhaps provenance hasn't been
completely overwritten with the newer encrypted files in my case but each time
I attempt to query provenance I get the ClassCastException.


If clearing the provenance repo when changing configurations would resolve
the issue can that step be included in the documentation (if needed I would
recommend including that step in the issues section)?
> 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
>
> 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)