[
https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
n h updated NIFI-2820:
----------------------
Comment: was deleted
(was: (For anyone who reach this issue by search) Answering my question using
another sterategy. Simply use this property:
bdfs.provenance.repository.indexed.attributes=alternate.identifier)
> Filtering "Data Provenance search" with "Alternate Identifier URI" returns
> only event of type "ADDINFO"
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2820
> URL: https://issues.apache.org/jira/browse/NIFI-2820
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.7.0
> Reporter: n h
>
> Setting:
> bdfs.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename,
> ProcessorID, Relationship, AlternateIdentifierURI
> run this scenario in 2 instances of nifi (nifi_1, nifi_2):
> 1. generate a flowfile in nifi_1.
> 2. adding "alternate.identifier" attribute using UpdateAttribute.
> (name=alternate.identifier, value=data:xyz)
> 3. sending the flowfile using site-to-site to nifi_2 (another remote
> instance) for processing (using a remote data which only nifi_2 has access to
> it)
> 4. send back the result flowfile from nifi_2 to nifi_1
> 5. in nifi_1, in data provenance window, search for all events using
> "alternate.identifier=data:xyz"
> Expected results: a list of all events that satisfies the condition:
> "alternate.identifier=data:xyz"
> Actual result:list has only one item : "ADDINFO" event
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
