[
https://issues.apache.org/jira/browse/NIFI-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260497#comment-16260497
]
ASF GitHub Bot commented on NIFI-4623:
--------------------------------------
GitHub user jwoschitz opened a pull request:
https://github.com/apache/nifi/pull/2281
NIFI-4623: Removed obsolete instability warning in documentation of n…
…ewer (>= 0_10) Kafka processors
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jwoschitz/nifi NIFI-4623
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2281.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2281
----
commit e07c540d94bfe82d5cf36c61aac376779040f5c6
Author: Janosch Woschitz <[email protected]>
Date: 2017-11-21T09:51:23Z
NIFI-4623: Removed obsolete instability warning in documentation of newer
(>= 0_10) Kafka processors
----
> Remove obsolete instability warning in documentation of newer (>= 0_10) Kafka
> processors
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-4623
> URL: https://issues.apache.org/jira/browse/NIFI-4623
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.4.0
> Reporter: Janosch Woschitz
> Priority: Minor
> Labels: documentation
>
> The documentation of all Kafka processors (publish and consume) does contain
> the following warning:
> {quote}Please note there are cases where the publisher can get into an
> indefinite stuck state. We are closely monitoring how this evolves in the
> Kafka community and will take advantage of those fixes as soon as we can. In
> the meantime it is possible to enter states where the only resolution will be
> to restart the JVM NiFi runs on.{quote}
> Based on a conversation on the dev mailing list, Joe Witt stated that this
> warning is not needed anymore for processors targeting Kafka 0_10 and beyond:
> {quote}It was there previously because it
> was observed that timeout conditions could cause threads to stay in a
> hung state and as the caller of the client we weren't in a position to
> resolve it. However, newer client libraries are better and I no
> longer have observed these issues personally. For the 0_10 or newer
> clients I think we can adjust the docs to indicate that these should
> work just fine.{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
