[
https://issues.apache.org/jira/browse/HBASE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053951#comment-14053951
]
Ted Yu commented on HBASE-11447:
--------------------------------
{code}
public Transaction begin(final TransactionIsolationLevel isolationLevel,
final int seconds);
{code}
Name the second parameter timeout or timeoutInSeconds ?
{code}
public Byte[] streamTo();
{code}
How about naming the above method:
{code}
public byte[] toByteArray() throws IOException;
{code}
Would it be simpler if TransactionTable has setTransaction() only ?
What would happen if setTransaction() is called on a TransactionTable which has
an active Transaction associated with it ?
Would it be better if TransactionTable is called TransactionTableInterface ?
bq. Also Transaction instances created by constructFrom can be used in parallel
with the Transaction instance from the beginner and with any other calls to
constructFrom in the same or different threads or processes.
By 'in parallel', do you mean 'interchangeably' ?
bq. If the Transaction Manager does not support the specified isolation level,
a NotSupportedException is thrown.
Would it make sense to add another method which returns the supported isolation
levels ?
> Proposal for a generic transaction API for HBase
> ------------------------------------------------
>
> Key: HBASE-11447
> URL: https://issues.apache.org/jira/browse/HBASE-11447
> Project: HBase
> Issue Type: New Feature
> Components: Client
> Affects Versions: 1.0.0
> Environment: Any.
> Reporter: John de Roo
> Priority: Minor
> Labels: features, newbie
> Fix For: 1.0.0
>
> Attachments: Proposal for a common transactional API for HBase
> v0.3_1.pdf, Re Proposal for a generic transaction API for HBase.htm
>
>
> HBase transaction management today is provided by a number of products, each
> implementing a different API, each having different strengths. The lack of a
> common API for transactional interfaces means that applications need to be
> coded to work with a specific Transaction Manager. This proposal outlines an
> API which, if implemented by the different Transaction Manager vendors would
> provide stability and choice to HBase application developers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
