[ https://issues.apache.org/jira/browse/PHOENIX-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025898#comment-15025898 ]
Mujtaba Chohan commented on PHOENIX-2446: ----------------------------------------- Some more observations: * Difference between row count of index vs base table is <= to the batch size for background running upserts when the index was created. * This row count difference is irrespective if index was created async vs sync. * Query with _no index_ hint after data load some time returns 2X row count of HBase base table for a while after data load finishes. > 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 > > 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)