[
https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345598#comment-15345598
]
ASF GitHub Bot commented on NIFI-2078:
--------------------------------------
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/563
NIFI-2078: External state management.
- Added ExternalStateManager to handle components' state managed
externally
- Added UI codes to display external state
- Added view/clear functionality to ConsumeKafka
- Added view/clear functionality to GetKafka
- Capture property value change, so that external state can be accessed
before onTrigger is called
TODO:
- Test with Kerberized Zookeeper and Kafka
- Fix Component State UI issues
- Fix Expression Language of ConsumeKafka properties
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijokarumawak/nifi nifi-2078
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/563.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #563
----
commit bb630fae8ce98c89fbfb4122e57bcf7fe83ba35f
Author: Koji Kawamura <[email protected]>
Date: 2016-06-23T02:29:32Z
NIFI-2078: External state management.
- Added ExternalStateManager to handle components' state managed
externally
- Added UI codes to display external state
- Added view/clear functionality to ConsumeKafka
- Added view/clear functionality to GetKafka
- Capture property value change, so that external state can be accessed
before onTrigger is called
----
> State management for processors whose states are managed externally
> -------------------------------------------------------------------
>
> Key: NIFI-2078
> URL: https://issues.apache.org/jira/browse/NIFI-2078
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
