Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-12679

Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf

Log workAgile BoardRank to TopRank to BottomAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Hi,

      I would like to propose a change that would make it possible for users to choose an implementation of IMetaStoreClient via HiveConf, i.e. hive-site.xml. Currently, in Hive the choice is hard coded to be SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There is no other direct reference to SessionHiveMetaStoreClient other than the hard coded class name in Hive.java and the QL component operates only on the IMetaStoreClient interface so the change would be minimal and it would be quite similar to how an implementation of RawStore is specified and loaded in hive-metastore. One use case this change would serve would be one where a user wishes to use an implementation of this interface without the dependency on the Thrift server.

      Thank you,
      Austin

      Attachments

        1. HIVE-12679.patch
          13 kB
          Austin Lee
        2. HIVE-12679.branch-2.3.patch
          13 kB
          Austin Lee
        3. HIVE-12679.branch-1.2.patch
          10 kB
          Austin Lee
        4. HIVE-12679.2.patch
          14 kB
          Austin Lee
        5. HIVE-12679.1.patch
          13 kB
          Austin Lee

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            moomindani Noritaka Sekiyama Assign to me
            austintlee Austin Lee

            Dates

              Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 1.5h
              1.5h

              Issue deployment