Uploaded image for project: 'Phoenix Omid'
  1. Phoenix Omid
  2. OMID-56

Integrate with Apache Phoenix

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:

      Description

      The current transaction implementation in Phoenix uses Tephra which is good when the number of rows in the transaction is small and the changes of a conflict are relatively rare. It's also not clear when the number of simultaneous transactions would max out given the single, global transaction manager component.

      Omid is very complimentary in this regard. Though the overhead for small transactions may be larger than Tephra, it will likely scale well as the number of rows in a transaction grows and has no global transaction manager.

      It'd be great to figure out the best way to integrate Omid with Phoenix. The trickiest issue may be with optimizing secondary indexes, in that conflict detection is not necessary for them. We could leave this optimization for the future and just treat them as any other HBase table. Perhaps a good first step would be to just turn on Omid transactions at the HBase level and then have Phoenix issue the appropriate Omid call for start transaction, commit transaction, and rollback transaction. It might just work.

        Attachments

          Activity

            People

            • Assignee:
              ohads Ohad Shaham
              Reporter:
              jamestaylor James R. Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: