drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paul-rogers <...@git.apache.org>
Subject [GitHub] drill pull request #833: DRILL-5496: Fix for failed Hive connection
Date Fri, 12 May 2017 18:02:51 GMT
GitHub user paul-rogers opened a pull request:

    https://github.com/apache/drill/pull/833

    DRILL-5496: Fix for failed Hive connection

    If the Hive server restarts, Drill either hangs or continually reports errors when retrieving
schemas. The problem is that the Hive plugin tries to handle connection failures, but does
not do so correctly for the secure connection case. The problem is complex, see DRILL-5496
for details.
    
    This is a workaround: we discard the entire Hive schema cache when we
    encounter an unhandled connection exception, then we rebuild a new one.
    
    This is not a proper fix; for that we'd have to restructure the code.
    
    This will, however, solve the immediate problem until we do the needed
    restructuring.

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

    $ git pull https://github.com/paul-rogers/drill DRILL-5496

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

    https://github.com/apache/drill/pull/833.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 #833
    
----
commit 10863164edfe8ef92058dd6b8568e9268d9b6978
Author: Paul Rogers <progers@maprtech.com>
Date:   2017-05-12T18:01:54Z

    DRILL-5496: Fix for failed Hive connection
    
    If the Hive server restarts, Drill either hangs or continually reports
    errors when retrieving schemas. The problem is that the Hive plugin
    tries to handle connection failures, but does not do so correctly for
    the secure connection case. The problem is complex, see DRILL-5496 for
    details.
    
    This is a workaround: we discard the entire Hive schema cache when we
    encounter an unhandled connection exception, then we rebuild a new one.
    
    This is not a proper fix; for that we'd have to restructure the code.
    
    This will, however, solve the immediate problem until we do the needed
    restructuring.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message