Re: InvokeHttp - Provenance Events

2024-02-26 Thread Gregory Foreman
Mark:

Ok, thanks for clarifying.

Greg

> On Feb 26, 2024, at 11:38 AM, Mark Payne  wrote:
> 
> Greg,
> 
> Yes, the Relationship is generally only populated for ROUTE events, such as 
> RouteOnAttribute.
> 
> Thanks
> -Mark
> 
> 
>> On Feb 26, 2024, at 11:34 AM, Gregory Foreman 
>>  wrote:
>> 
>> Hello:
>> 
>> I am having an issue with the InvokeHttp processor provenance events.  No 
>> Relationship field is populated in the Provenance Event / Details page.  Is 
>> this expected?  I am trying to query provenance for Relationship other than 
>> “Response" so that I can view failed flow files.
>> 
>> The system is running Nifi 1.23.2, the nifi.properties is properly set to 
>> index this Field, and the RouteOnAttribute processor is setting this Field 
>> as expected.
>> 
>> Thanks,
>> Greg
> 



Re: InvokeHttp - Provenance Events

2024-02-26 Thread Mark Payne
Greg,

Yes, the Relationship is generally only populated for ROUTE events, such as 
RouteOnAttribute.

Thanks
-Mark


> On Feb 26, 2024, at 11:34 AM, Gregory Foreman 
>  wrote:
> 
> Hello:
> 
> I am having an issue with the InvokeHttp processor provenance events.  No 
> Relationship field is populated in the Provenance Event / Details page.  Is 
> this expected?  I am trying to query provenance for Relationship other than 
> “Response" so that I can view failed flow files.
> 
> The system is running Nifi 1.23.2, the nifi.properties is properly set to 
> index this Field, and the RouteOnAttribute processor is setting this Field as 
> expected.
> 
> Thanks,
> Greg



InvokeHttp - Provenance Events

2024-02-26 Thread Gregory Foreman
Hello:

I am having an issue with the InvokeHttp processor provenance events.  No 
Relationship field is populated in the Provenance Event / Details page.  Is 
this expected?  I am trying to query provenance for Relationship other than 
“Response" so that I can view failed flow files.

The system is running Nifi 1.23.2, the nifi.properties is properly set to index 
this Field, and the RouteOnAttribute processor is setting this Field as 
expected.

Thanks,
Greg