How are your HandleHttpResponse timeouts set?

On Thu, 11 Jul 2019, at 16:02, Carlos Manuel Fernandes (DSI) wrote:
> Hello, I think i discover the problem with content not claimed, its wired, 
> the problem only happens in nifi web services handleHttpRequest-> .. -> 
> HandleHttpResponse.

> 

> For example, in this flow : GenerateFlowFile->FetchFile->PutFile after two 
> minutes the content is claimed.

> But if call HandleHttpRequest-> FetchFile->PutFile->HandleHttpResponse the 
> content is not claimed.

> 

> Can Someone repeat this test on version 1.9.2 to verify I’m right or wrong?

> 

> Thanks

> 

> Carlos

> 

> 

> *From:* Mark Payne [mailto:[email protected]] 
> *Sent:* terça-feira, 9 de julho de 2019 15:47
> *To:* [email protected]
> *Subject:* Re: Content Claim

> 

> Carlos,

> 

> A FlowFile can only reference a single claim at a time. It initially 
> referenced ...-40. It then changed its reference to ...-42. At that point, it 
> no longer referenced ...-40.


> 

> On Jul 9, 2019, at 10:45 AM, Carlos Manuel Fernandes (DSI) 
> <[email protected]> wrote:

> 

> Mark,

> 

> In my exemple the flow file with id b82ee4e3-7957-4262-ab9d-0ddbd97c4f36 
> reference two content claims : 1562670204881-40, 1562670205203-42. After the 
> flow Finish, the references from the flowfile to the two content claims are 
> erased?

> 

> Thanks,

> 

> Carlos

> 

> 

> 

> 

> 

> *From:* Mark Payne [mailto:[email protected]] 
> *Sent:* terça-feira, 9 de julho de 2019 15:29
> *To:* [email protected]
> *Subject:* Re: Content Claim

> 

> Carlos, 

> 

> Many FlowFiles can reference the same Content Claim. The Content Claim will 
> be kept around until there are no longer

> any FlowFiles referencing it. At that point, it will continue to stay around 
> until the FlowFile Repository is checkpointed

> (which happens every 2 minutes by default). Once the FlowFile Repo is 
> checkpointed, it will either destroy the Content Claim

> or archive it (assuming it is no longer in use), depending on whether or not 
> archiving of the content is enabled in nifi.properties.

> 


> 
> 

> On Jul 9, 2019, at 10:17 AM, Carlos Manuel Fernandes (DSI) 
> <[email protected]> wrote:

> 

> Hello, sorry i dont finish the last mail.

> 

> I had some problems with data on content repository not claimed using nifi 
> version 1.9.2. Trying to understand da root cause I make a simple flow : 
> generate flow file with 10 bytes -> replaceText -> logAttributte and see in 
> data provenance :

> 

> Type FlowFIleID ComponentName Claim Identifier

> Create b82ee4e3-7957-4262-ab9d-0ddbd97c4f36 GenerateFlowFile 1562670204881-40

> CONTENT_MODIFIED b82ee4e3-7957-4262-ab9d-0ddbd97c4f36 CONTENT_MODIFIED 
> 1562670205203-42

> Drop b82ee4e3-7957-4262-ab9d-0ddbd97c4f36 LogAttribute 1562670205203-42

> 

> The problem I see is the original data with id 1562670204881-40 is not 
> dropped . How will the content with id 1562670204881-40 claimed?

> 

> Thanks,

> 

> Carlos

> 

Reply via email to