[jira] [Created] (BIGTOP-3455) Hive 2.2.x bug with DBTokenStore

["Luca Toscano (Jira)" <ji...@apache.org>]

Luca Toscano created BIGTOP-3455:
------------------------------------

             Summary: Hive 2.2.x bug with DBTokenStore
                 Key: BIGTOP-3455
                 URL: https://issues.apache.org/jira/browse/BIGTOP-3455
             Project: Bigtop
          Issue Type: Bug
          Components: hive
    Affects Versions: 1.4.0, 1.5.0
            Reporter: Luca Toscano


Hi everybody,

I have recently worked on a sneaky bug between Oozie and Hive, described in:

https://issues.apache.org/jira/browse/HIVE-17368

I added the hive.cluster.delegation.token.store.class = org.apache.hadoop.hive.thrift.DBTokenStore to support high availability for the Hive Metastore. The idea is that Hive sessions (when using auth like Kerberos) are stored on the DB rather than in memory, so multiple metastores can share the same set of clients (this is my understanding, very simplified view). With hive 2.2.3 on 1.4 I see the same issues described in  HIVE-17368, so what I did was finding the fix for the 2.x branch (since the official fix went out for hive 3.x) and I rebuilt the hive packages via Docker:

https://github.com/apache/hive/commit/b3a6e524a6cb17893cbbeb26a877b0196ba16e21

More specifically, I created bigtop-packages/src/common/hive/patch1-HIVE-17368.diff and added the content of the above link (using the .diff suffix to get the patch). 

Everything works now :)

I then checked the hive version on Bigtop 1.5, and it should be 2.3.6, that doesn't seem to have the fix from what I see in https://hive.apache.org/downloads.html (none of the 2.3.x seem to have it, and 2.4 was hasn't been released yet).

Do you think that it would be ok to add the patch (last minute I know) before the 1.5 release gets out?

Thanks in advance!

Luca



--
This message was sent by Atlassian Jira
(v8.3.4#803005)