GitHub user yestinchen opened a pull request:

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

    [FLINK-7309][hotfix] fix NullPointerException when selecting null fields

    ## What is the purpose of the change
    
    This pull request addresses FLINK-7309, adds null check before applying 
unboxing on input fields.
    
    ## Brief change log
    
    - Add null check before applying unboxing on input fields.
    
    ## Verifying this change
    
    This change added tests and can be verified as follows:
     - Added test case: select null field from a Timestamp type field.
    
    ## 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)
    


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

    $ git pull https://github.com/yestinchen/flink FLINK-7309

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

    https://github.com/apache/flink/pull/4479.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 #4479
    
----
commit 7cbbd13b723df11e72ccb115b5266104b0b01183
Author: Yestin <[email protected]>
Date:   2017-08-04T09:21:03Z

    [FLINK-7309][hotfix] fix NullPointerException when selecting null fields.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to