[jira] [Commented] (PHOENIX-2446) Immutable index - Index vs base table row count does not match when index is created during data load

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor commented on PHOENIX-2446:
---------------------------------------

Different idea than the sleep: what if we ran the upsert/select at a lower priority than normal? That way the other work would naturally finish first? Second idea is if we did a manual flush after the create index, but before the upsert/select. Would you mind trying those ideas?

> Immutable index - Index vs base table row count does not match when index is created during data load
> -----------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2446
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2446
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>            Reporter: Mujtaba Chohan
>            Assignee: Thomas D'Silva
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2446.patch
>
>
> I'll add more details later but here's the scenario that consistently produces wrong row count for index table vs base table for immutable async index.
> 1. Start data upsert
> 2. Create async index
> 3. Trigger M/R index build
> 4. Keep data upsert going in background during step 2,3 and a while after M/R index finishes.
> 5. End data upsert. 
> Now count with index enabled vs count with hint to not use index is off by a large factor. Will get a cleaner repro for this issue soon.



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