phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2582) Prevent need of catch up query when creating non transactional index
Date Thu, 16 May 2019 05:15:00 GMT

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

Kadir OZDEMIR commented on PHOENIX-2582:
----------------------------------------

[~tdsilva], I wrote a comment on this Jira and then deleted it. If you have seen my comment,
please ignore it. I think this issue and the related issues have been fixed by PHOENIX-5018
where I eliminated the use of UPSERT SELECT for building indexes.

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message