[NIFI-2078] State management for processors whose states are managed externally

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: Core Framework
• Assignee: Koji Kawamura
• Reporter: Koji Kawamura
• Created: 22/Jun/16 06:04
• Updated: 13/Oct/16 13:05

Description

Inherently by the nature of a given processor it may involve state managed by itself (using nifi state management), or can be managed by some external service it interacts with (kafka's offset), and theoretically some might have both going on. With the new state management, we're giving users a way to reset state managed by nifi for a given processor. But it doesnt apply to those processors who have external state.
we should consider offering a way to reset state that allows a processor to call out to whatever external store it impacts

Issue Links

• is blocked by: NIFI-2364 Node shouldn't be disconnected from a cluster when clear component state operation gets error related to underlying data source
• is blocked by: NIFI-2363 CLUSTER scope state should be viewed/cleared from primary node
• is related to: NIFI-2093 Clear state link on Component State window is hidden
• is related to: NIFI-2094 Component State Description is not displayed correctly
• relates to: NIFI-2442 ExternalStateManager should support Expression Language evaluation
• relates to: NIFI-2441 View state fails with a JS error: "Cannot read property 'canRead' of undefined"
• links to: GitHub Pull Request #563

Sub-Tasks

• ExternalStateManager should support Expression Language evaluation: Open