GitHub user cjmatta opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/684

    Zeppelin 639

    ### What is this PR for?
    JDBCInterpreter should check for a null object before simply calling 
`getString`. This will prevent poorly implemented JDBC drivers from causing a 
NullPointerException.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    
    ### Is there a relevant Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-639
    
    ### How should this be tested?
    Run the `testSelectQueryWithNull` test included with this PR.
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No

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

    $ git pull https://github.com/cjmatta/incubator-zeppelin ZEPPELIN-639

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

    https://github.com/apache/incubator-zeppelin/pull/684.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 #684
    
----
commit 0a0ad72b777dbfb79c8d00df5f017fe7dbc8ce5c
Author: vgmartinez <viktor.manuel.gar...@gmail.com>
Date:   2016-01-22T16:40:05Z

    fix parse property in interprete name

commit f228b84058a6731be6a910821db494f8cf5c0eb7
Author: vgmartinez <viktor.manuel.gar...@gmail.com>
Date:   2016-01-22T22:04:21Z

    add test for parse propertyKey

commit 6db8d0aae0d78b01f0bb3b1adba77d3f45045a77
Author: Chris Matta <cma...@mapr.com>
Date:   2016-02-02T19:07:36Z

    Merge branch 'master' into bug_628

commit 4247356bdf129cc6e168cb6c5894eac9a1bfabb1
Author: Chris Matta <cma...@mapr.com>
Date:   2016-02-02T20:52:44Z

    Added check for null in resultSet. Added tests.

----


---
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