[
https://issues.apache.org/jira/browse/PHOENIX-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141774#comment-16141774
]
Hudson commented on PHOENIX-2582:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1750 (See
[https://builds.apache.org/job/Phoenix-master/1750/])
PHOENIX-4118 Disable tests in ImmutableIndexIT till PHOENIX-2582 is (samarth:
rev dd008f4fe4e67836a6fb362843c9618e4e518182)
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/ImmutableIndexIT.java
> Prevent need of catch up query when creating non transactional index
> --------------------------------------------------------------------
>
> Key: PHOENIX-2582
> URL: https://issues.apache.org/jira/browse/PHOENIX-2582
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Thomas D'Silva
> Assignee: Thomas D'Silva
>
> If we create an index while we are upserting rows to the table its possible
> we can miss writing corresponding rows to the index table.
> If a region server is writing a batch of rows and we create an index just
> before the batch is written we will miss writing that batch to the index
> table. This is because we run the inital UPSERT SELECT to populate the index
> with an SCN that we get from the server which will be before the timestamp
> the batch of rows is written.
> We need to figure out if there is a way to determine that are pending batches
> have been written before running the UPSERT SELECT to do the initial index
> population.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
