Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.92.0
    • Coprocessors
    • None
    • Reviewed
    • Hide
      Adds new HTable.coprocessorProxy() and HTable.coprocessorExec() calls, along with server-side hooks for registering user RPC protocol handlers. Together these allow the invocation and execution of custom server-side code configured as coprocessors.

      Adds pluggable RPC engines as a first step towards alternate RPC implementations. This adds a field for the RPC protocol interface on connection setup, so it's not RPC wire compatible with previous versions.
      Show
      Adds new HTable.coprocessorProxy() and HTable.coprocessorExec() calls, along with server-side hooks for registering user RPC protocol handlers. Together these allow the invocation and execution of custom server-side code configured as coprocessors. Adds pluggable RPC engines as a first step towards alternate RPC implementations. This adds a field for the RPC protocol interface on connection setup, so it's not RPC wire compatible with previous versions.

    Description

      "High-level call interface for clients. Unlike RPC, calls addressed to rows or ranges of rows. Coprocessor client library resolves to actual locations. Calls across multiple rows automatically split into multiple parallelized RPCs"

      Generic multicall RPC facility which incorporates this and multiget/multiput/multidelete and parallel scanners.

      Group and batch RPCs by region server. Track and retry outstanding RPCs. Ride over region relocations.

      Support addressing by explicit region identifier or by row key or row key range.

      Include a facility for merging results client side.

      Attachments

        1. HBASE-2002_final.patch
          148 kB
          Gary Helmling

        Issue Links

        Activity

          People

            ghelmling Gary Helmling
            apurtell Andrew Kyle Purtell
            Votes:
            0 Vote for this issue
            Watchers:
            Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                In order to see discussions, first confirm access to your Slack account(s) in the following workspace(s): ASF