You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Rob Fellows (Jira)" <ji...@apache.org> on 2026/09/16 14:50:00 UTC
[jira] [Created] (NIFI-16352) UI - Disable Component State single-entry clear when the listing is partial
Rob Fellows created NIFI-16352:
----------------------------------
Summary: 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
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)