phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4557) Move index state related columns to their own table
Date Thu, 25 Jan 2018 21:22:00 GMT


James Taylor commented on PHOENIX-4557:

We may only set INDEX_DISABLE_TIMESTAMP on rows with a NULL TENANT_ID in which case we can
prevent the full table scan with a simple prefix filter (of which there will only be a small
number). The only caveat is local indexes and indexes on views. It's unclear if we handle
these today. This needs some investigation.

> Move index state related columns to their own table
> ---------------------------------------------------
>                 Key: PHOENIX-4557
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Priority: Major
> To prevent full table scans on SYSTEM.CATALOG to determine out-of-sync indexes, we should
factor out any state related information and put this into a SYSTEM.INDEX_STATE table instead.
The table would only contain rows for tables that are in an invalid/unexpected state. Since
the row count would be expected to be very low, a full table scan over this table would be
tolerable. We'd need to join to this table when we send the PTable back from the server to
the client.

This message was sent by Atlassian JIRA

View raw message