[
https://issues.apache.org/jira/browse/PHOENIX-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243821#comment-17243821
]
Istvan Toth edited comment on PHOENIX-6236 at 12/4/20, 8:22 AM:
----------------------------------------------------------------
Thanks for your review [~kozdemir], it's always bets to get information from
the horse's mouth.
I have split the immutable index consistency description for the consistent and
old indexing, to be similar to the mutable indexing description, and changed
the ordering.
I've checked the second issue, but the description seems to be right:
{noformat}
create table my_table (k1 integer primary key, v1 integer, v2 integer, v3
integer);
CREATE INDEX my_index2 ON my_table (v1) INCLUDE (v2); /* note that v3 is not
included */
explain SELECT v3 FROM my_table WHERE v1 = 1;
+-------------------------------------------------------------------+----------------+---------------+-------------+
| PLAN |
EST_BYTES_READ | EST_ROWS_READ | EST_INFO_TS |
+-------------------------------------------------------------------+----------------+---------------+-------------+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN FULL SCAN OVER MY_TABLE | null
| null | null |
| SERVER FILTER BY V1 = 1 | null
| null | null |
+-------------------------------------------------------------------+----------------+---------------+-------------+
explain SELECT /*+ INDEX(my_table my_index2) */ v3 FROM my_table WHERE v1 = 1;
+---------------------------------------------------------------------------------+----------------+---------------+-------------+
| PLAN
| EST_BYTES_READ | EST_ROWS_READ | EST_INFO_TS |
+---------------------------------------------------------------------------------+----------------+---------------+-------------+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN FULL SCAN OVER MY_TABLE
| null | null | null |
| SKIP-SCAN-JOIN TABLE 0
| null | null | null |
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER MY_INDEX2
[1] | null | null | null |
| SERVER FILTER BY FIRST KEY ONLY
| null | null | null |
| DYNAMIC SERVER FILTER BY "MY_TABLE.K1" IN ($24.$26)
| null | null | null |
+---------------------------------------------------------------------------------+----------------+---------------+-------------+{noformat}
was (Author: stoty):
Thanks for your review [~kozdemir], it's always bets to get information from
the horse's mouth.
I have split the immutable index consistency description for the consistent and
old indexing, to be similar to the mutable indexing description, and changed
the ordering.
I've checked the second issue, but the description seems to be right:
{noformat}
create table my_table (k1 integer primary key, v1 integer, v2 integer, v3
integer);
CREATE INDEX my_index2 ON my_table (v1) INCLUDE (v2); /* note that v3 is not
included */
explain SELECT v3 FROM my_table WHERE v1 = 1;
+-------------------------------------------------------------------+----------------+---------------+-------------+
| PLAN | EST_BYTES_READ | EST_ROWS_READ | EST_INFO_TS |
+-------------------------------------------------------------------+----------------+---------------+-------------+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN FULL SCAN OVER MY_TABLE | null |
null | null |
| SERVER FILTER BY V1 = 1 | null | null | null |
+-------------------------------------------------------------------+----------------+---------------+-------------+
2 rows selected (0.016 seconds)
explain SELECT /*+ INDEX(my_table my_index2) */ v3 FROM my_table WHERE v1 = 1;
+---------------------------------------------------------------------------------+----------------+---------------+-------------+
| PLAN
| EST_BYTES_READ | EST_ROWS_READ | EST_INFO_TS |
+---------------------------------------------------------------------------------+----------------+---------------+-------------+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN FULL SCAN OVER MY_TABLE
| null | null | null |
| SKIP-SCAN-JOIN TABLE 0
| null | null | null |
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER MY_INDEX2
[1] | null | null | null |
| SERVER FILTER BY FIRST KEY ONLY
| null | null | null |
| DYNAMIC SERVER FILTER BY "MY_TABLE.K1" IN ($24.$26)
| null | null | null |
+---------------------------------------------------------------------------------+----------------+---------------+-------------+{noformat}
> Document Strongly Consistent Global Indexes on website
> ------------------------------------------------------
>
> Key: PHOENIX-6236
> URL: https://issues.apache.org/jira/browse/PHOENIX-6236
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Attachments: PHOENIX-6236.website.patch,
> Secondary_Indexing_current.htm, secondary_indexing.html
>
>
> Document Strongly Consistent Local Indexing, and the update procedure on the
> website
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
