You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by cleroux <gi...@git.apache.org> on 2018/04/23 08:11:09 UTC

[GitHub] storm pull request #2642: Fix NullPointerException when apply() returns null

GitHub user cleroux opened a pull request:

    https://github.com/apache/storm/pull/2642

    Fix NullPointerException when apply() returns null

    A null List<Object> is a valid return value from RecordTranslator.apply() if the ConsumerRecord is invalid.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cleroux/storm master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/2642.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 #2642
    
----
commit 399c816d3f7aef42a86bee3e8d1bcd2b54bc3b4c
Author: cleroux <le...@...>
Date:   2018-04-23T07:54:55Z

    Fix NullPointerException when apply() returns null

----


---

[GitHub] storm issue #2642: Fix NullPointerException when apply() returns null

Posted by srdo <gi...@git.apache.org>.
Github user srdo commented on the issue:

    https://github.com/apache/storm/pull/2642
  
    @cleroux Thanks for the fix. The change looks good to me. Please raise an issue at https://issues.apache.org/jira/secure/Dashboard.jspa, and include the issue number in the PR title and the commit message. It helps us track which branches the fix has been applied to.


---

[GitHub] storm pull request #2642: [STORM-3043] Fix NullPointerException when apply()...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/storm/pull/2642


---

[GitHub] storm issue #2642: [STORM-3043] Fix NullPointerException when apply() return...

Posted by srdo <gi...@git.apache.org>.
Github user srdo commented on the issue:

    https://github.com/apache/storm/pull/2642
  
    +1, thanks @cleroux, merged to master. Please open another PR against 1.x-branch, so this fix can make it into 1.x releases too :)


---