[
https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402977#comment-15402977
]
ASF GitHub Bot commented on NIFI-2078:
--------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
@ijokarumawak there is a lot of great work here but the various tickets
that are included in this one PR are making it difficult to review and test.
Could we close this PR and break it out into separate ones for each ticket so
that they can be addressed individually? That would make it much more efficient
to get the bugs fixes into master and properly test the new external state
management.
Also could we move NIFI-2078 out of 1.0 to 1.1? This is an important new
feature with API implications and it would be nice to finishing reviewing once
the other API changes take effect and the various UI blocking bugs are
addressed.
> 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)
