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 2016/01/12 21:54:40 UTC
[jira] [Created] (PHOENIX-2591) Minimize transaction
commit/rollback for DDL
James Taylor created PHOENIX-2591:
-------------------------------------
Summary: Minimize transaction commit/rollback for DDL
Key: PHOENIX-2591
URL: https://issues.apache.org/jira/browse/PHOENIX-2591
Project: Phoenix
Issue Type: Bug
Reporter: James Taylor
Assignee: Thomas D'Silva
Seems that the number of times we commit/rollback transactions during DDL operations could be improved. See TransactionUtil.getTableTimestamp() for example. There'd also be another couple when MutationState.commitWriteFence() is called when a CREATE INDEX is performed too.
I realize we're doing this to get the transaction read pointer to "catch up" to the current time, as we use the read pointer as our "current time" for transactional tables. However, what would the impact be if we used the transaction write pointer instead?
At a minimum, we need to document what we're doing before we forget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)