[
https://issues.apache.org/jira/browse/NIFI-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126021#comment-16126021
]
ASF GitHub Bot commented on NIFI-4290:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/2083
NIFI-4290: Ensure that the InFlightMessageTracker is instantiated whe…
…n getTracker() is called
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/markap14/nifi NIFI-4290
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2083.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 #2083
----
commit d1405b7ae418a718a3391ed8301a48a504a9910b
Author: Mark Payne <[email protected]>
Date: 2017-08-14T17:23:35Z
NIFI-4290: Ensure that the InFlightMessageTracker is instantiated when
getTracker() is called
----
> PublishKafkaRecord_0_10: failed to process due to
> java.lang.NullPointerException
> --------------------------------------------------------------------------------
>
> Key: NIFI-4290
> URL: https://issues.apache.org/jira/browse/NIFI-4290
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.0
> Environment: NiFi 1.4 Master
> Confluent Kafka 3.2
> Reporter: Mayank Rathi
> Assignee: Mark Payne
> Attachments: Kafka_Record_1.4_Bug.docx, Kafka_Record_1.4_Bug.xml,
> nifi-app_latest.log, nifi-app.log
>
>
> Hello All,
> I am moving data to Kafka using NiFi's PublishKafkaRecord processor. I am
> using ConfluentSchemaRegistry Controller service and getting below error:
> 2017-08-11 20:54:25,937 ERROR [Timer-Driven Process Thread-4]
> o.a.n.p.k.pubsub.PublishKafkaRecord_0_10
> PublishKafkaRecord_0_10[id=b3c03961-015d-1000-0946-79ccbe2ffbbd]
> PublishKafkaRecord_0_10[id=b3c03961-015d-1000-0946-79ccbe2ffbbd] failed to
> process due to java.lang.NullPointerException; rolling back session: {}
> java.lang.NullPointerException: null
> I do not see any error on Kafka side.
> Attached are the logs after setting processors in Debug mode. Here is the
> flow:
> ExecuteSQL --> SplitAvro --> PublishKafkaRecord_0_10
> Thanks!!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
