[
https://issues.apache.org/jira/browse/PHOENIX-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Gwalani updated PHOENIX-7304:
--------------------------------------
Description:
The first 2 bytes of any View Index row are reserved for view index Ids. If
there is an API to get list all existing unique view index IDs, client can
leverage it for different usecase
Eg: If a client need to scan and filter view index table, based on the list of
data table keys, skip-scan filter cannot be directly leveraged since row key is
not the prefix of view index. Instead if a list of unique view index IDs is
already available, skip scan filter can be used with combination of view index
IDs and knonw keys of data table, which would ultimately improve scan
performance by avoiding a full table scan.
Phoenix Query to list all view index IDs for a physical view index table
<TABLE_NAME>.
{{SELECT DISTINCT VIEW_INDEX_ID FROM SYSTEM.CATALOG WHERE TABLE_NAME IN (SELECT
DISTINCT TABLE_NAME FROM SYSTEM.CATALOG WHERE LINK_TYPE = 2 AND TENANT_ID IS
NULL AND COLUMN_FAMILY = '<TABLE_NAME>') AND VIEW_INDEX_ID is not null;}}
was:
The first 2 bytes of any View Index row are reserved for view index Ids. If
there is an API to get list all existing unique view index IDs, client can
leverage it for different usecase
Eg: If a client need to scan and filter view index table, based on the list of
data table keys, skip-scan filter cannot be directly leveraged since row key is
not the prefix of view index. Instead if a list of unique view index IDs is
already available, skip scan filter can be used with combination of view index
IDs and knonw keys of data table, which would ultimately improve scan
performance by avoiding a full table scan.
> Add support for getting list of View Index IDs for any View Index Physical
> Table
> --------------------------------------------------------------------------------
>
> Key: PHOENIX-7304
> URL: https://issues.apache.org/jira/browse/PHOENIX-7304
> Project: Phoenix
> Issue Type: Task
> Reporter: Himanshu Gwalani
>
> The first 2 bytes of any View Index row are reserved for view index Ids. If
> there is an API to get list all existing unique view index IDs, client can
> leverage it for different usecase
> Eg: If a client need to scan and filter view index table, based on the list
> of data table keys, skip-scan filter cannot be directly leveraged since row
> key is not the prefix of view index. Instead if a list of unique view index
> IDs is already available, skip scan filter can be used with combination of
> view index IDs and knonw keys of data table, which would ultimately improve
> scan performance by avoiding a full table scan.
> Phoenix Query to list all view index IDs for a physical view index table
> <TABLE_NAME>.
> {{SELECT DISTINCT VIEW_INDEX_ID FROM SYSTEM.CATALOG WHERE TABLE_NAME IN
> (SELECT DISTINCT TABLE_NAME FROM SYSTEM.CATALOG WHERE LINK_TYPE = 2 AND
> TENANT_ID IS NULL AND COLUMN_FAMILY = '<TABLE_NAME>') AND VIEW_INDEX_ID is
> not null;}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
