GitHub user sohami opened a pull request:
https://github.com/apache/drill/pull/628
DRILL-4964: Drill fails to connect to hive metastore after hive metasâ¦
â¦tore is restarted unless drillbits are restarted also
Changes: For certain methods in DrillHiveMetaStoreClient like
getAllDatabases and getAllTables the HiveMetaStoreClient
wraps the exception of type MetaException and
TException both into MetaException. So in case of connection
failure which is thrown as TException it is difficult
to categorize at DrillClient level. Hence the fix
is to close older connection and reconnect in case of
these 2 api's. In all other cases proper set of exceptions
are thrown where we can handle each one individually.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sohami/drill DRILL-4964
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/628.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 #628
----
commit 95477151e9a5b28a121ffe6a879006e4333039c4
Author: Sorabh Hamirwasia <[email protected]>
Date: 2016-10-26T01:52:01Z
DRILL-4964: Drill fails to connect to hive metastore after hive metastore
is restarted unless drillbits are restarted also
Changes: For certain methods in DrillHiveMetaStoreClient like
getAllDatabases and getAllTables the HiveMetaStoreClient
wraps the exception of type MetaException and
TException both into MetaException. So in case of connection
failure which is thrown as TException it is difficult
to categorize at DrillClient level. Hence the fix
is to close older connection and reconnect in case of
these 2 api's. In all other cases proper set of exceptions
are thrown where we can handle each one individually.
----
---
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.
---