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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.6.0
• Fix Version/s: 4.7.0
• Assignee: Thomas D'Silva
• Reporter: Mujtaba Chohan
• Created: 23/Nov/15 19:12
• Updated: 22/Jan/16 06:26
• Resolved: 22/Jan/16 05:57

Description

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.

Issue Links

• is related to: PHOENIX-2582 Prevent need of catch up query when creating non transactional index