[ 
https://issues.apache.org/jira/browse/NIFI-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Chaffelson updated NIFI-15533:
-------------------------------------
    Description: 
It is possible to configure QueryDatabaseTable Properties such as Additional 
Where Clause, Columns to Return, etc. with Parameter references that do not 
exist in the attached Parameter context.
This causes the Processor to be marked as Invalid when observed directly in the 
UI, however if you go to the parent Process Group it is not reported as in 
Invalid and the Progress Group is able to be started.

!image-2026-01-30-22-29-00-127.png|width=370,height=185!

!image-2026-01-30-22-29-56-921.png|width=614,height=265!

  was:
It is possible to configure QueryDatabaseTable Properties such as Additional 
Where Clause, Columns to Return, etc. with Parameter references that do not 
exist in the attached Parameter context.
This causes the Processor to be marked as Invalid when observed directly in the 
UI, however if you go to the parent Process Group it is not reported as in 
Invalid and the Progress Group is able to be started.


!image-2026-01-30-22-29-00-127.png!


> QueryDatabaseTable Invalid when referenced Parameters do not exist, but does 
> not report to parent PG
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-15533
>                 URL: https://issues.apache.org/jira/browse/NIFI-15533
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Daniel Chaffelson
>            Priority: Minor
>         Attachments: image-2026-01-30-22-29-00-127.png, 
> image-2026-01-30-22-29-10-751.png, image-2026-01-30-22-29-56-921.png
>
>
> It is possible to configure QueryDatabaseTable Properties such as Additional 
> Where Clause, Columns to Return, etc. with Parameter references that do not 
> exist in the attached Parameter context.
> This causes the Processor to be marked as Invalid when observed directly in 
> the UI, however if you go to the parent Process Group it is not reported as 
> in Invalid and the Progress Group is able to be started.
> !image-2026-01-30-22-29-00-127.png|width=370,height=185!
> !image-2026-01-30-22-29-56-921.png|width=614,height=265!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to