phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2460) Implement scrutiny command to validate whether or not an index is in sync with the data table
Date Tue, 25 Jul 2017 00:54:00 GMT

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

James Taylor commented on PHOENIX-2460:
---------------------------------------

Proposed syntax would be:
{code}
EXECUTE SCRUTINY <full table name>
{code}
This would return a ResultSet which would contain information about the scrutiny: IS_INVALID,
INVALID_ROW_COUNT, SCANNED_ROW_COUNT, and any other useful metadata.

If the table name resolves to a table, then all indexes on the table will be scrutinized.
If the table name resolves to an index, then only that index will be scrutinized.

If we want to introduce a MR-based scrutiny, then we could support an ASYNC keyword in this
statement. Also useful would be some kind of syntax (a property like FAIL_FAST=true might
be easiest) that determines if the scrutiny should stop immediately after finding an invalid
row or continue.

> Implement scrutiny command to validate whether or not an index is in sync with the data
table
> ---------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2460
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2460
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Thomas D'Silva
>
> We should have a process that runs to verify that an index is valid against a data table
and potentially fixes it if discrepancies are found. This could either be a MR job or a low
priority background task.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message