[GitHub] nifi issue #2509: NIFI-543 Added annotation to indicate processor should run...

[zenfenan <gi...@git.apache.org>]

Github user zenfenan commented on the issue:

    https://github.com/apache/nifi/pull/2509
  
    @mcgilman I understand the points you have made. They are valid. In particular, I like the last one which is how this might have benefit in building a flow in a standalone node with appropriate nodes and then save it to the registry.
    
    I just have three questions:
    - `All Nodes` option should be disabled if the component is marked as `PrimaryNodeOnly`. That should be the case in both standalone as well as cluster scenario. Correct?
    - Processors which were previously added to the canvas i.e. those who were not `executionNodeRestricted` and had `executionNode` as `ALL` but after this change, those processors will have the `All Nodes` option disabled and the user will only have the ability to switch to `Primary Node`, post which the user will never be able to select `All Nodes` again. Technically that's correct since the processor is supposed to be run only on the primary node. You feel that is okay? Do you see any inconsistency in UX?
    - One more thing is, in general, I used to feel that `Execution Nodes` doesn't make sense in a standalone context so showing the dropdown still has got me thinking whether we should display it or not. But your point on showing the dropdown for all the components and in all cases (standalone or cluster) seems to make it consistent and also the understanding on how this will be well suited in actual enterprise scenarios where most enterprise customers probably use standalone node to get the flow/template ready and save it to registry and will actually import it to a cluster. The question, here, again is with respect to the UX. With this change, we will be showing the dropdown all the time for all the processors in standalone case. Do you see any issues/inconsistency with the way the user would perceive this new change?


---