Ah sorry I confused "which node the processor is on" with "where it is
scheduled to run". Sounds like you would need the fix Mark suggested.
I was just looking at the code of HandleHttpRequest and I think it
avoids the problem I was talking about... I was thinking of the case
where the
It seems reasonable to me to add a `ExecutionNode getExecutionNode()` method to
ProcessContext. This enum already exists in nifi-api, but I don't believe that
it's exposed anywhere to the Processor itself.
> On Aug 16, 2019, at 11:32 AM, Peter Wicks (pwicks) wrote:
>
> Bryan,
>
> I'm
Bryan,
I'm familiar with the getNodeTypeProvider method. Unfortunately, this does not
differentiate between processors that are scheduled to run only on the Primary
node and those that are scheduled to run on all of them.
So you're saying, a better fix would be to properly call
