You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2016/01/08 18:47:39 UTC

[jira] [Created] (PHOENIX-2582) Creating an index while a batch of rows is being written leads to missing rows in the index table

Thomas D'Silva created PHOENIX-2582:
---------------------------------------

             Summary: Creating an index while a batch of rows is being written leads to missing rows in the index table
                 Key: PHOENIX-2582
                 URL: https://issues.apache.org/jira/browse/PHOENIX-2582
             Project: Phoenix
          Issue Type: Bug
            Reporter: 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.

[~jamestaylor] 



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