You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2017/04/21 00:52:04 UTC

[jira] [Created] (NIFI-3722) Handle provenance repository encryption status change on startup

Andy LoPresto created NIFI-3722:
-----------------------------------

             Summary: Handle provenance repository encryption status change on startup
                 Key: NIFI-3722
                 URL: https://issues.apache.org/jira/browse/NIFI-3722
             Project: Apache NiFi
          Issue Type: Sub-task
          Components: Core Framework
    Affects Versions: 1.2.0
            Reporter: Andy LoPresto
            Assignee: Andy LoPresto


If the provenance repository changes from encrypted -> unencrypted or vice-versa on startup, the application should handle the change. 

* Unencrypted -> encrypted: Attempt to create a {{EventIdFirstSchemaRecordReader}} instance to read the existing events into memory and write them back using {{EncryptedSchemaRecordWriter}}
* Encrypted -> unencrypted: Attempt to create a {{EncryptedSchemaRecordReader}} instance to read the existing events into memory and write them back using {{EventIdFirstSchemaRecordWriter}} or {{ByteArraySchemaRecordWriter}} depending on the repository implementation class. This depends on the key(s) for the key IDs used still being available via {{nifi.properties}}. 

This process may be very slow given large existing repositories, so a standalone tool should also be made available to perform this process outside of the running app. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)