That make sense. Thanks Koji for prompt replies. Appreciate it.
Thankyou.
On Tue, Jul 30, 2019 at 6:20 AM Koji Kawamura
wrote:
> The tryLock method does not block if a lock is already acquired by other
> thead.
>
>
The tryLock method does not block if a lock is already acquired by other
thead.
Thanks for reply.
Hmm, that should explain the behavior we noted.
But I see an instance level lock which is protecting the update Mapping
method. *Shouldn't that eventually block other threads from accessing the
old mapping?*
Or may that this locking was added later - version 1.9 or something?
Hi Ameer,
Is the ReplaceTextWithMapping's 'Concurrent Tasks' set to grater than 1?
Since ReplaceTextWithMapping only reload at a single thread, other
threads may use old mapping until the loading thread complete
refreshing mapping definition.
Thanks,
Koji
On Wed, Jul 24, 2019 at 4:28 AM Ameer
Inline.
On Mon, Jul 22, 2019 at 2:17 AM Koji Kawamura
wrote:
> Hi Ameer,
>
> How is ReplaceTextWithMapping 'Mapping File Refresh Interval' configured?
>
[Ameer] It is configured to 1sec - the lowest value allowed.
> By default, it's set to '60s'. So,
> 1. If ReplaceTextWithMapping ran with the
Hi Ameer,
How is ReplaceTextWithMapping 'Mapping File Refresh Interval' configured?
By default, it's set to '60s'. So,
1. If ReplaceTextWithMapping ran with the old mapping file
2. and the mapping file was updated for the next processing
3. then the flow started processing another CSV file right
Correcting Typo.
On Fri, Jul 19, 2019 at 2:03 PM Ameer Mawia wrote:
> Guys,
>
> It seems that NIFI ReplaceTextWithMapping Processors has a BUG with
> Refreshing its Mapped file. We are using its functionality in PROD and
> getting odd behaviour.
>
> Our USAGE Scenario:
>
>- We use NIFI
Guys,
It seems that NIFI ReplaceTextWithMapping Processors has a BUG with
Refreshing its Mapped file. We are using its functionality in PROD and
getting odd behaviour.
Our USAGE Scenario:
- We use NIFI primarily as a TRANSFORMATION Tool.
- Our flow involves:
1. Getting a raw csv
