[
https://issues.apache.org/jira/browse/NIFI-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Fellows updated NIFI-16352:
-------------------------------
Status: Patch Available (was: In Progress)
> UI - Disable Component State single-entry clear when the listing is partial
> ---------------------------------------------------------------------------
>
> Key: NIFI-16352
> URL: https://issues.apache.org/jira/browse/NIFI-16352
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Rob Fellows
> Assignee: Rob Fellows
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h2. Problem
> When GET /state is truncated (totalEntryCount greater than the returned
> entries; cap is 5000 via SortedStateUtils.MAX_COMPONENT_STATE_ENTRIES), the
> Component State dialog already sets partialResults and shows “Showing partial
> results.” Per-entry delete is still offered.
> Clear-entry does not send “delete this key.” The UI POSTs the *visible
> remainder* of the map. The server requires that payload to be the *full live
> map minus exactly one key*
> (StandardComponentStateDAO.hasExactlyOneKeyRemoved). A partial listing fails
> that check with:
> Unable to remove a state key for component … Exactly one key removal is
> supported.
> Reproduced on DebugFlow with Generate State Entries above the GET cap (e.g.
> clearing debug_state_key_00000).
> h2. Fix
> When partialResults is true:
> * Do not offer per-entry delete (hide or disable the actions column)
> * Do not dispatch clearComponentStateEntry
> * Keep *Clear state* for the whole map
> * Optional tooltip/copy explaining why single-entry clear is unavailable on
> a partial listing
> h2. Out of scope
> * Changing the clear-entry API
> * Raising the 5000-entry GET cap
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
