[
https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402946#comment-15402946
]
ASF GitHub Bot commented on NIFI-2078:
--------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
Continuing the comment on "linger.ms", it appears when the "linger.ms"
property is used in PublishKafka it yields the same results. Going forward it
looks like we should be taking two steps:
1: Change our default in PutKafka to match the Kafka default. Looking at
the [Kafka documentation](http://kafka.apache.org/documentation.html) the
default value for "linger.ms" is 0 seconds, for no delay.
2: Figure out whether the mishandling of the property is a problem in our
Processors or the underlying libraries. This may be tricky to do and I can
start but I will probably need help. @olegz could you help here?
> 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)
