[
https://issues.apache.org/jira/browse/PHOENIX-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated PHOENIX-2656:
------------------------------------
Attachment: PHOENIX-2656.patch
[~jamestaylor]
Can you please review?
Thanks,
Thomas
> Shield Phoenix from Tephra repackaging
> --------------------------------------
>
> Key: PHOENIX-2656
> URL: https://issues.apache.org/jira/browse/PHOENIX-2656
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Thomas D'Silva
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2656.patch
>
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
