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

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

Github user JPercivall commented on the issue:

    https://github.com/apache/nifi/pull/563
  
    Hey @ijokarumawak, I tried testing this using Consume/Publish Kafka with 
Kafka 0.10.0 but I'm not seeing any state come up with I view state for 
ConsumeKafka. In the below screenshots you can see the data is following but no 
state is being stored. I have tried all 3 values of the "offset reset" for 
ConsumeKafka but that doesn't make a difference. Is there something special I 
should be doing?
    
    ![screen shot 2016-07-29 at 12 54 58 
pm](https://cloud.githubusercontent.com/assets/11302527/17256496/c2e0005c-558b-11e6-8616-ec40ded55155.png)
    ![screen shot 2016-07-29 at 12 54 09 
pm](https://cloud.githubusercontent.com/assets/11302527/17256501/cb3bd4ba-558b-11e6-896e-378f8a08c51f.png)
    



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

Reply via email to