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

Hudson commented on PHOENIX-2478:
---------------------------------

SUCCESS: Integrated in Phoenix-master #1070 (See 
[https://builds.apache.org/job/Phoenix-master/1070/])
PHOENIX-2478 Rows committed in transaction overlapping index creation (jtaylor: 
rev 30c2e75556c365b059f23d43de5ac272f92aa285)
* phoenix-core/src/main/java/org/apache/phoenix/exception/SQLExceptionCode.java
* 
phoenix-core/src/main/java/org/apache/phoenix/compile/DelegateMutationPlan.java
* pom.xml
* phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexIT.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
* 
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* phoenix-core/src/it/java/org/apache/phoenix/tx/TransactionIT.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/MutationState.java
* phoenix-core/src/main/java/org/apache/phoenix/util/SchemaUtil.java
* 
phoenix-core/src/main/java/org/apache/phoenix/compile/PostIndexDDLCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/TableRef.java


> Rows committed in transaction overlapping index creation are not populated
> --------------------------------------------------------------------------
>
>                 Key: PHOENIX-2478
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2478
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2478.patch, PHOENIX-2478_v2.patch, 
> PHOENIX-2478_v3.patch, PHOENIX-2478_v4.patch
>
>
> For a reproducible case, see IndexIT.testCreateIndexAfterUpsertStarted() and 
> the associated FIXME comments for PHOENIX-2446.
> The case that is failing is when a commit starts before an index exists, but 
> commits after the index build is completed. For transactional data, this is 
> problematic because the index gets a timestamp after the commit of the data 
> table mutation and thus these mutations won't be seen during the commit. 
> Also, when the index is being built, the data hasn't yet been committed and 
> thus won't be part of the initial index build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to