Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Sun, 25 Sep 2016 18:49:20 +0000 (UTC)
From: "n h (JIRA)" <jira@apache.org>
To: issues@nifi.apache.org
Message-ID: <JIRA.13007460.1474828921000.658943.1474829360852@Atlassian.JIRA>
In-Reply-To: <JIRA.13007460.1474828921000@Atlassian.JIRA>
References: <JIRA.13007460.1474828921000@Atlassian.JIRA> <JIRA.13007460.1474828921396@arcas>
Subject: [jira] [Updated] (NIFI-2820) Filtering "Data Provenance search"
 with "Alternate Identifier URI" returns only event of type "ADDINFO"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 25 Sep 2016 18:49:22 -0000


     [ https://issues.apache.org/jira/browse/NIFI-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

n h updated NIFI-2820:
----------------------
    Description: 
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

  was:
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, 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


> 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
>            Reporter: n h
>             Fix For: 1.1.0
>
>
> 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)