You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/11/13 03:08:11 UTC
[jira] [Created] (PHOENIX-2411) Allow Phoenix to participate as
transactional component
James Taylor created PHOENIX-2411:
-------------------------------------
Summary: Allow Phoenix to participate as transactional component
Key: PHOENIX-2411
URL: https://issues.apache.org/jira/browse/PHOENIX-2411
Project: Phoenix
Issue Type: Improvement
Reporter: James Taylor
Frameworks such as Cask's CDAP support a means of individual components to participate in a transaction. To support this, Phoenix would need to:
- Provide a means of passing in the serialized state of a transaction as a connection property. An easy way to do this is to base64 encode the byte[] of the serialized transaction.
- Provide a statement or statements to run and flush any uncommitted data after execution. The caller could use the Statement.addBatch(String sqlStmt) multiple times and call Statement.executeBatch() to run more than one statement at a time.
- Optionally provide a means of getting back the potentially new transaction state (as checkpointing may have been required as a result of running the batch of statements).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)