[PHOENIX-5376] Bulk loading data tables with indexes leads to index rows with incorrect timestamps

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.0.0, 4.14.2
• Assignee: Unassigned
• Reporter: Kadir OZDEMIR
• Created: 26/Jun/19 02:35
• Updated: 14/Dec/21 17:36

Description

Bulk loading data on a table is done directly on HFiles by bypassing Phoenix. A table and its indexes are loaded independently. This results in timestamp mismatch between data table rows and their corresponding index rows. It is known that this mismatch causes consistency issues. Consistent global indexes introduced by PHOENIX-5156 and PHOENIX-5211 require a data table row and the corresponding index rows should have the same timestamp all the time. Thus, it is required that data and index table rows should get the same timestamp during bulk loading too.

Issue Links

• relates to: PHOENIX-6611 Fix IndexTool -snap option and set VERIFIED in PhoenixIndexImportDirectReducer