Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-19200

make hbase-client only depend on ZKAsyncRegistry and ZNodePaths

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.0.0-beta-1, 2.0.0
    • Client, Zookeeper
    • None
    • Reviewed
    • Hide
      ConnectionImplementation now uses asynchronous connections to zookeeper via ZKAsyncRegistry to get cluster id, master address, meta region location, etc.
      Since ZKAsyncRegistry uses curator framework, this change purges a lot of zookeeper dependencies in hbase-client.
      Now hbase-client only depends on only ZKAsyncRegistry, ZNodePaths and the newly introduced ZKMetadata.
      Show
      ConnectionImplementation now uses asynchronous connections to zookeeper via ZKAsyncRegistry to get cluster id, master address, meta region location, etc. Since ZKAsyncRegistry uses curator framework, this change purges a lot of zookeeper dependencies in hbase-client. Now hbase-client only depends on only ZKAsyncRegistry, ZNodePaths and the newly introduced ZKMetadata.

    Description

      So that we can move most of the zookeeper related code out of hbase-client module.

      Attachments

        1. HBASE-19200.patch
          30 kB
          Duo Zhang
        2. HBASE-19200-v1.patch
          31 kB
          Duo Zhang
        3. HBASE-19200-v2.patch
          43 kB
          Duo Zhang
        4. HBASE-19200-v3.patch
          184 kB
          Duo Zhang
        5. HBASE-19200-v4.patch
          191 kB
          Duo Zhang
        6. HBASE-19200-v5.patch
          198 kB
          Duo Zhang

        Issue Links

          Activity

            People

              zhangduo Duo Zhang
              zhangduo Duo Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: