[PHOENIX-5835] When data columns get TTLed, and run IndexScrutiny or validation we marked them as invalid rows

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Gokcen Iskender
• Created: 13/Apr/20 17:59
• Updated: 14/Apr/20 22:59

Description

We do index writes as full row writes. This means all columns keep get re-written to index and they have a current timestamp.

However, if there is a column that did not get updated for a long time (like Created_By type of columns that don't change) the regular scan that IndexScrutiny uses doesn't return this column even though we might see it in the raw scan.

IndexScrutiny mark these rows as invalid because data table had TTL columns and index table have it.

Index inline validation also marks these as "Index has extra columns" if the column got TTLed.

Issue Links

• is cloned by: PHOENIX-5841 When data columns get TTLed, we need inline index validation to publish a metric for this