[ 
https://issues.apache.org/jira/browse/NIFI-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486700#comment-17486700
 ] 

ASF subversion and git services commented on NIFI-9628:
-------------------------------------------------------

Commit 230ed9c98d5b704ab0803d14441531948b0915da in nifi's branch 
refs/heads/main from markap14
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=230ed9c ]

NIFI-9628: Added a uiOnly flag when requesting Controller Service det… (#5712)

* NIFI-9628: Added a uiOnly flag when requesting Controller Service details and 
the list of Controller Services. This allows us to return much less data when 
retrieving these resources.

* NIFI-9628: Addressed review feedback; added uiOnly flag for controller 
service run-status and references also

* NIFI-9628: Fixed checkstyle issues by removing unused imports

This closes #5712 

> When UI retrieves 1 or more Controller Services, we should avoid pulling back 
> extraneous information
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-9628
>                 URL: https://issues.apache.org/jira/browse/NIFI-9628
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Core UI
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.16.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When the UI fetches a Controller Service or the list of Controller Services 
> for a given Process Group, the Referencing Components that are returned 
> contain the components' property values and property descriptors. This 
> information is not used by the UI but can result in a very large payload 
> being returned. We should filter out these property values and descriptors 
> for this use case.
> Because we want to maintain backward compatibility, we should introduce a 
> {{uiOnly}} query parameter for the appropriate endpoints, in much the same 
> way that we do for Process Groups



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to