Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-4278

Implement pure client side transactional index maintenance

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.14.0, 5.0.0
    • Labels:
      None

      Description

      The index maintenance for transactions follows the same model as non transactional tables - coprocessor based on data table updates that looks up previous row value to perform maintenance. This is necessary for non transactional tables to ensure the rows are locked so that a consistent view may be obtained. However, for transactional tables, the time stamp oracle ensures uniqueness of time stamps (via transaction IDs) and the filtering handles a scan seeing the "true" last committed value for a row. Thus, there's no hard dependency to perform this on the server side.

      Moving the index maintenance to the client side would prevent any RS->RS RPC calls (which have proved to be troublesome for HBase). It would require returning more data to the client (i.e. the prior row value), but this seems like a reasonable tradeoff.

        Attachments

        1. PHOENIX-4278_addendum1.patch
          107 kB
          James Taylor
        2. PHOENIX-4278_5.x-HBase-2.0.patch
          90 kB
          Rajeshbabu Chintaguntla
        3. PHOENIX-4278_v2.patch
          94 kB
          James Taylor
        4. PHOENIX-4278.4.x-HBase-1.3.v1.patch
          41 kB
          Ohad Shacham

          Issue Links

            Activity

              People

              • Assignee:
                ohads Ohad Shacham
                Reporter:
                jamestaylor James Taylor
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: