mcgilman opened a new pull request, #10976:
URL: https://github.com/apache/nifi/pull/10976

   … processor dialog.
   
   ## Summary
   
   When a processor is annotated with `@TriggerSerially`, the "Concurrent 
Tasks" field in the Edit Processor dialog should be disabled since the 
framework enforces single-threaded execution regardless of the configured 
value. The old jQuery-based UI (removed in NIFI-13313) handled this by 
disabling the input, excluding the value from save payloads, and skipping it 
during change detection. The current Angular UI did not carry over this 
behavior.
   
   This PR restores that treatment with an improvement: in addition to 
disabling the field, the info icon tooltip now explains why it is disabled.
   
   ### Changes
   
   - **Disable the concurrent tasks form control** in the constructor when 
`supportsParallelProcessing` is `false` (the inverse of `@TriggerSerially`)
   - **Exclude `concurrentlySchedulableTaskCount` from the update payload** 
when the processor does not support parallel processing, matching the pattern 
used for `runDurationMillis` / `supportsBatching()`
   - **Dynamic tooltip on the info icon** -- when the processor supports 
parallel processing, the standard description is shown; when it does not, the 
tooltip explains that the processor does not support parallel processing
   - **Unit tests** covering both the `supportsParallelProcessing: true` and 
`supportsParallelProcessing: false` cases, verifying form control state and 
tooltip text
   
   ### Files Changed
   
   - `edit-processor.component.ts` -- Added `supportsParallelProcessing()` and 
`concurrentTasksTooltip()` methods; disabled form control in constructor; 
guarded payload in `submitForm()`
   - `edit-processor.component.html` -- Changed tooltip from static string to 
dynamic `[tooltipInputData]="concurrentTasksTooltip()"`
   - `edit-processor.component.spec.ts` -- Extracted test fixture data to 
module scope; added 4 new tests across two describe blocks


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to