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

ASF GitHub Bot commented on NIFI-3594:
--------------------------------------

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-compatibility is not yet provided). 


> 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)

Reply via email to