GitHub user zjureel opened a pull request:

    https://github.com/apache/flink/pull/4562

    [FLINK-7402] Fix ineffective null check in NettyMessage#write()

    ## What is the purpose of the change
    
    Fix ineffective null check in NettyMessage#write()
    
    ## Brief change log
    
    *(for example:)*
      - *Add null check and remove unnecessary null check*
    
    
    ## Verifying this change
    
    *(Please pick either of the following options)*
    
    No test case
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)
      - If yes, how is the feature documented? (not applicable / docs / 
JavaDocs / not documented)
    


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

    $ git pull https://github.com/zjureel/flink FLINK-7402

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

    https://github.com/apache/flink/pull/4562.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 #4562
    
----
commit e289b37cf8adce56876b47ee33ed161058bf64e6
Author: zjureel <zjur...@gmail.com>
Date:   2017-08-18T06:43:34Z

    [FLINK-7402] Fix ineffective null check in NettyMessage#write()

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to