GitHub user LosD opened a pull request:

    https://github.com/apache/metamodel/pull/133

    Don't get killed by Hive SQLExceptions when finding default schema name

    This will allow Hive to throw its exceptions while we're trying to 
determine the default schema name, without that failing.
    
    Also fixes a problem where columns types without a width would fail by 
specifying maximum allowed column width for VARCHAR types. (Maybe I should have 
fixed this in another PR, but it broke the Hive integration test, which drove 
me mad... Let me know if I should split them).
    
    Fixes METAMODEL-1119

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

    $ git pull https://github.com/LosD/metamodel 
bug/METAMODEL-1119-workaround-hive-issue

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

    https://github.com/apache/metamodel/pull/133.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 #133
    
----
commit 4d81aef06eb9a93fbb70fb63b8d9645f25741615
Author: Dennis Du Krøger <[email protected]>
Date:   2016-10-10T14:32:43Z

    Don't get killed by Hive SQLExceptions when finding default schema name
    
    This will allow Hive to throw its exceptions while weøre trying to 
determine the default schema name, without that failing.
    
    Also fixes a problem where columns types without a width would fail by 
specifying maximum allowed column width for VARCHAR types. (Maybe I should have 
fixed this in another PR, but it broke the Hive integration test, which drove 
me mad... Let me know if I should split them).
    
    Fixes METAMODEL-1119

----


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