[
https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401002#comment-15401002
]
ASF GitHub Bot commented on NIFI-2078:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/563
@JPercivall I was able to reproduce the behavior with Kafka 0.10.0. But
figured out the cause comes from a different change.
[NIFI-2355](https://issues.apache.org/jira/browse/NIFI-2355) and its PR
#715 added permission check to table sort comparator, in nf-component-state.js.
I think it shouldn't be added to state table, since a given user won't have
record level permission difference for component state.
#715 has the same change for changes nf-controller-services.js and other JS
files. I assume adding the permission change to nf-component-state.js was a
mistake. By removing the change from nf-component-state.js, I was able to view
external state with Kafka 0.10.0 Broker.
It's worth noting that I got the same JS error with ListFile when I viewed
its state, so the problem is not limited to external state.
Failed NIFI-2441 for that 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.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)
