[PHOENIX-2656] Shield Phoenix from Tephra repackaging

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.7.0
• Assignee: Thomas D'Silva
• Reporter: James R. Taylor
• Created: 05/Feb/16 19:07
• Updated: 09/Feb/16 03:38
• Resolved: 09/Feb/16 03:38

Description

When TEPHRA-151 happens, the Tephra coprocessors will get repackaged from co.cask.tephra.hbase11.coprocessor to org.apache.tephra. This would force us to modify the metadata of existing users since we attach this coprocessor to transactional Phoenix tables.

At a minimum, we should create our own PhoenixTransactionProcessor which delegates to Tephra's TransactionProcessor. If there are other touch points like this (I'm not aware of others), we should do the same. I think we're ok for the Transaction Manager since we have our own startup script we could muck with (plus this is really a test-only script and deployment would be different).