GitHub user randerzander opened a pull request:

    https://github.com/apache/zeppelin/pull/2117

    ZEPPELIN-2241: JDBC interpreter throws npe on connecting to any db that has 
a schema with "null" name

    ### What is this PR for?
    A few sentences describing the overall goals of the pull request's commits.
    First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html
    
    Prevents JDBC interpreter from throwing a stacktrace when the database has 
a schema with no name (null).
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
    * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]
    
    https://issues.apache.org/jira/browse/ZEPPELIN-2241
    
    ### How should this be tested?
    Outline the steps to test the PR here.
    
    Use JDBC interpreter to connect to any database that has a schema without a 
name. Apache Phoenix in particular has such a schema by default.
    
    ### Screenshots (if appropriate)
    
    ### 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/randerzander/zeppelin master

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

    https://github.com/apache/zeppelin/pull/2117.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 #2117
    
----
commit 0101296833161629609eef71b5df904152f15841
Author: Randy Gelhausen <rgel...@gmail.com>
Date:   2017-03-10T04:59:59Z

    ZEPPELIN-2241: JDBC interpreter throws npe on connecting to any db that has 
a schema with "null" name

----


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