[
https://issues.apache.org/jira/browse/NIFI-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990845#comment-15990845
]
ASF GitHub Bot commented on NIFI-3721:
--------------------------------------
Github user alopresto commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1713#discussion_r114130189
--- Diff: nifi-docs/src/main/asciidoc/administration-guide.adoc ---
@@ -2110,18 +2110,19 @@ To store provenance events in memory instead of on
disk (in which case all event
set this property to
org.apache.nifi.provenance.VolatileProvenanceRepository. This leaves a
configurable number of Provenance Events in the Java heap, so the number
of events that can be retained is very limited.
-As of Apache NiFi 1.2.0, a third option is available:
org.apache.nifi.provenance.WriteAheadProvenanceRepository.
-This implementation was created to replace the
PersistentProvenanceRepository. The PersistentProvenanceRepository was
originally written with the simple goal of persisting
+As of Apache NiFi 1.2.0, a third and fourth option are available:
`org.apache.nifi.provenance.WriteAheadProvenanceRepository` and
`org.apache.nifi.provenance.EncryptedWriteAheadProvenanceRepository`.
+This implementation was created to replace the
`PersistentProvenanceRepository`. The `PersistentProvenanceRepository` was
originally written with the simple goal of persisting
Provenance Events as they are generated and providing the ability to
iterate over those events sequentially. Later, it was desired to be able to
compress the data so that
more data could be stored. After that, the ability to index and query the
data was added. As requirements evolved over time, the repository kept changing
without any major
-redesigns. When used in a NiFi instance that is responsible for processing
large volumes of small FlowFiles, the PersistentProvenanceRepository can
quickly become a bottleneck.
-The WriteAheadProvenanceRepository was then written to provide the same
capabilities as the PersistentProvenanceRepository while providing far better
performance.
-Changing to the WriteAheadProvenanceRepository is easy to accomplish, as
the two repositories support most of the same properties.
-*Note Well*, however, the follow caveat: The
WriteAheadProvenanceRepository will make use of the Provenance data stored by
the PersistentProvenanceRepository. However, the
--- End diff --
Will do. Thanks.
> Provide documentation for encrypted provenance repository
> ---------------------------------------------------------
>
> Key: NIFI-3721
> URL: https://issues.apache.org/jira/browse/NIFI-3721
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Documentation & Website
> Affects Versions: 1.2.0
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Critical
> Labels: documentation, encryption, provenance, security
>
> The {{EncryptedWriteAheadProvenanceRepository}} is a new feature for Apache
> NiFi and requires substantial documentation on its inner workings, various
> configuration options, performance, extensibility and future enhancements,
> design decisions, and potential obstacles. This should be documented in both
> the Admin Guide and User Guide.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
