nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-2078) State management for processors whose states are managed externally
Date Tue, 05 Jul 2016 16:32:11 GMT

    [ https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362723#comment-15362723
] 

ASF GitHub Bot commented on NIFI-2078:
--------------------------------------

Github user JPercivall commented on the issue:

    https://github.com/apache/nifi/pull/563
  
    Starting to review.
    
    Unless if I'm missing something, why is external state only added for GetKafka and ConsumeKafka?
Aren't there many other processors that manage state externally?


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

Mime
View raw message