6.20.00.13
> >>>
> >>> * Oracle JDBC version: 12.2.0.1.0
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> In addition, I have done similar test on LookupAttribute (Oracle)
> processor. The same situation happened; flow
t;>
>>> * Oracle JDBC version: 12.2.0.1.0
>>>
>>>
>>>
>>>
>>>
>>> In addition, I have done similar test on LookupAttribute (Oracle)
>>> processor. The same situation happened; flow files were penalized and the
>>> queue o
; * Oracle JDBC version: 12.2.0.1.0
>>
>>
>>
>>
>>
>> In addition, I have done similar test on LookupAttribute (Oracle) processor.
>> The same situation happened; flow files were penalized and the queue on
>> upstream connection of LookupAttribute (Oracle
le)
> processor. The same situation happened; flow files were penalized and the
> queue on upstream connection of LookupAttribute (Oracle) increased..
>
>
>
> Thank you in advance,
>
>
>
> --Bilal
>
>
>
>
>
> *From:* Edward Armes
> *Sent:* 26 Ekim 20
files were penalized and the queue on
upstream connection of LookupAttribute (Oracle) increased..
Thank you in advance,
--Bilal
From: Edward Armes
Sent: 26 Ekim 2021 Salı 23:40
To: users@nifi.apache.org
Subject: Re: Penalty feature of Processor (Disable)
Hi Bilal,
Can you just confirm
, do you think to add a new feature (Rollback On Failure) for
> LookupAttribute processor like PutHiveQL processor?
>
>
>
> Thank you for helping,
>
>
>
> --Bilal
>
>
>
>
>
> *From:* Edward Armes
> *Sent:* 26 Ekim 2021 Salı 01:32
> *To:
Subject: Re: Penalty feature of Processor (Disable)
Having a quick look at the lookupAttribute code it looks like it takes a
Optional<> from the call to the configured service. So I wonder if its worth
adding the logic to service instead so that on erroring it can either return a
missing
>
> > >>>>
> > >>>>
> > >>>> LookupAttribute (Teradata) ---(failure & unmatched) --->
> LookupAttribute (Oracle)
> > >>>>
> > >>>>
> > >>>>
> > >>>>
;
> >>>> LookupAttribute (Oracle)
> >>>>
> >>>>
> >>>>
> >>>> This flows works well and LookupAttribute (Teradata) penalizes to flow
> >>>> files when Teradata DB is down. Therefore, the queue on upstream
> >>>
t;>>> files when Teradata DB is down. Therefore, the queue on upstream
>>>> connection of LookupAttribute (Teradata) increases. But, we don't want to
>>>> that LookupAttribute (Teradata) penalizes to flow files. We want to that
>>>> LookupAttribute (Terad
>> LookupAttribute (Teradata) penalizes to flow files. We want to that
>>> LookupAttribute (Teradata) processor forwards flow files to failure
>>> downstream connection when all failure situation on LookupAttribute
>>> (Teradata). Thus, LookupAttribute (Oracle) can pr
LookupAttribute (Teradata) processor forwards flow files to failure
>> downstream connection when all failure situation on LookupAttribute
>> (Teradata). Thus, LookupAttribute (Oracle) can process flow files which
>> cannot process on LookupAttribute (Teradata).
Teradata). Thus, LookupAttribute (Oracle) can process flow files which
> cannot process on LookupAttribute (Teradata).
>
>
>
> Is it possible to disable penalty feature of processor or is there any
> solution which you can suggest for this situation.
>
>
>
> Tha
solution which you can suggest
Thank you in advance,
--Bilal
From: Mark Payne
Sent: 25 Ekim 2021 Pazartesi 17:25
To: users@nifi.apache.org
Subject: Re: Penalty feature of Processor (Disable)
Bilal,
In the Settings tab, you can set the “Penalty Duration” to “0 secs”.
Thanks
-Mark
On Oct
w files which cannot process on
LookupAttribute (Teradata).
Is it possible to disable penalty feature of processor or is there any solution
which you can suggest for this situation.
Thank you in advance,
--Bilal
obase
TEL: +90216 527 30 00
FAX: +90216 527 31 11
[http://www.obase.com/images/signa
nection when all failure situation on LookupAttribute (Teradata). Thus,
LookupAttribute (Oracle) can process flow files which cannot process on
LookupAttribute (Teradata).
Is it possible to disable penalty feature of processor or is there any solution
which you can suggest for this situation.
Th
16 matches
Mail list logo
