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)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
