[ 
https://issues.apache.org/jira/browse/PHOENIX-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498559#comment-16498559
 ] 

Hudson commented on PHOENIX-4762:
---------------------------------

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #148 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/148/])
PHOENIX-4762 Performance regression with transactional immutable indexes 
(jtaylor: rev f3119320b6d263252a790c6a5cd96dce5a714ed6)
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/transaction/OmidTransactionContext.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/execute/PhoenixTxIndexMutationGenerator.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/IndexUtil.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/transaction/TephraTransactionContext.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/execute/MutationState.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/transaction/PhoenixTransactionContext.java


> Performance regression with transactional immutable indexes
> -----------------------------------------------------------
>
>                 Key: PHOENIX-4762
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4762
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4762_v1.patch
>
>
> The introduction of the TAL caused a performance regression with immutable 
> indexes. Prior to the TAL, index rows would not be transaction participants 
> so they would not take up client memory. Instead, on rollback, we re-generate 
> the index deletes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to