Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-26149 Further improvements on ConnectionRegistry implementations
  3. HBASE-28436

Use connection url to specify the connection registry information

    XMLWordPrintableJSON

Details

    • Reviewed
    • Hide
      Allow sepcifying the connection info of a HBase cluster through an URI.

      For now, we support two types of scheme:
      hbase+rpc, which indicates RpcConnectionRegistry
      hbase+zk, which indicates ZKConnectionRegistry

      For hbase+rpc, we will use the authority part of the URI as bootstrap node when creating RpcConnectionRegistry.
      For hbase+zk, we will use the authority part of the URI as zookeeper quorum, and the path part of the URI as zookeeper parent znode when creating ZKConnectionRegistry.

      We introduced several new methods in ConnectionRegistry class which accept URI as parameter. And if we can not find a registered factory for the scheme of the URI, we will fallback to use the old logic, to create ConnectionRegistry through configurations.
      Show
      Allow sepcifying the connection info of a HBase cluster through an URI. For now, we support two types of scheme: hbase+rpc, which indicates RpcConnectionRegistry hbase+zk, which indicates ZKConnectionRegistry For hbase+rpc, we will use the authority part of the URI as bootstrap node when creating RpcConnectionRegistry. For hbase+zk, we will use the authority part of the URI as zookeeper quorum, and the path part of the URI as zookeeper parent znode when creating ZKConnectionRegistry. We introduced several new methods in ConnectionRegistry class which accept URI as parameter. And if we can not find a registered factory for the scheme of the URI, we will fallback to use the old logic, to create ConnectionRegistry through configurations.

    Description

      As describe in this email from ndimiduk

      https://lists.apache.org/thread/98wqlkqvlnmpx3r7yrg9mw4pqz9ppofh

      The first advantage here is that, we can encode the connection registry implementation in the scheme of the connection url, so for replication, we can now support cluster key other than zookeeper, which is important for us to remove zookeeper dependency on our public facing APIs.

      Attachments

        Issue Links

          blocks

          Improvement - An improvement or enhancement to an existing feature or task. HBASE-28425 Allow specify cluster key without zookeeper in replication

          • Major - Major loss of function.
          • Open
          breaks

          Bug - A problem which impairs or prevents the functions of the product. HBASE-28555 ThriftConnection does not need ConnectionRegistry

          • Major - Major loss of function.
          • Open
          relates to

          Sub-task - The sub-task of the issue HBASE-28547 Support specifying connection registry configuration through queries of the connection uri

          • Major - Major loss of function.
          • In Progress
          links to

          Web Link GitHub Pull Request #5770

          Web Link GitHub Pull Request #5847

          Web Link GitHub Pull Request #5855

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: