[
https://issues.apache.org/jira/browse/NIFI-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990948#comment-15990948
]
ASF GitHub Bot commented on NIFI-3594:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1686
@YolandaMDavis Thanks Yolanda.
During most of my testing, I did clear the repositories between application
starts when switching the implementation (`rm -rf provenance_repository/
content_repository/ flowfile_repository/` from `$NIFI_HOME/conf`). I did run
tests (at the time) where I left the repository intact (in each direction) and
my notes are:
```
-Verified switching from encrypted prov repo to plain will not allow access
to previously-written events
-Error in app log
-Suppress stacktrace?
-App still starts
-UI error dialog on prov query
-New provenance events overwrite previous
-New prov queries work
-Verified switching from plain prov repo to encrypted will not allow
access to previously-written events
-Error in app log
-Suppress stacktrace?
-App still starts
-UI error dialog on prov query
-New provenance events overwrite previous
-New prov queries work
```
I will re-evaluate those scenarios as soon as I finish reviewing PR 1712
for Bryan.
I do think suppressing the stacktrace and providing a more descriptive
error is a good idea and will tackle that as well. If it is determined there is
a simple reason your queries were not working, great. If not, adding
documentation instructing repository removal may be necessary.
> 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)
