Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1686
Yolanda,
I can reproduce your described issue. I believe the difference is that when
I tested and did not clear the existing provenance repository, I was switching
between `EncryptedWriteAheadProvenanceRepository` and
`WriteAheadProvenanceRepository` which both use a `SchemaRecordReader` that can
be cross-cast (`EncryptedRecordSchemaReader` extends
`EventIdFirstRecordSchemaReader`), so the class cast exception wasn't
occurring. However, if you test by first using
`PersistentProvenanceRepository`, this uses `ByteArraySchemaRecordReader`,
which implements the same `RecordReader` interface but cannot be cast. As
`PersistentProvenanceRepository` is the existing option that most people will
be using, production switch over will encounter this issue. I will try to
improve this user experience (opening a separate sub-task to do that). For now,
I've included documentation in [NIFI-3721] stating that the existing repository
should be erased when switching (as this is a new feature and backward-com
patibility is not yet provided).
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
