You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2016/08/02 01:15:21 UTC

[jira] [Updated] (NIFI-2078) State management for processors whose states are managed externally

     [ https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koji Kawamura updated NIFI-2078:
--------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.1.0
           Status: Open  (was: Patch Available)

Spoked with Joe Witt and Joe Percivall about release target. Since there is not enough time to go though review & test cycle to be in 1.0. Also, cancel the patch to break it down to smaller PRs only focusing individual JIRA issue.

> 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.1.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)