[jira] [Reopened] (PHOENIX-6854) Salted global indexes do not work for queries with uncovered columns
[
https://issues.apache.org/jira/browse/PHOENIX-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana reopened PHOENIX-6854:
> Salted global indexes do not work for queries with uncovered columns
>
>
> Key: PHOENIX-6854
> URL: https://issues.apache.org/jira/browse/PHOENIX-6854
> Project: Phoenix
> Issue Type: Bug
>Reporter: Kadir Ozdemir
>Assignee: Tanuj Khurana
>Priority: Major
> Fix For: 5.2.0, 5.1.3
>
>
> With an index hint, global indexes can be used for queries with uncovered
> columns. However, when the data table is salted, Phoenix does not project the
> columns correctly for queries with uncovered columns, and thus the result set
> returns wrong columns. For example, the following select statement returns
> 'b' instead of 'bcde'.
>
> {code:java}
> create table T1 (id varchar not null primary key, val1 varchar, val2 varchar,
> val3 varchar) SALT_BUCKETS=4;
> upsert into T1 values ('b', 'bc', 'bcd', 'bcde');
> create index I1 on T1 (val1) include (val2);
> select /*+ INDEX(T1 I1)*/ val3 from T1 WHERE val1 = 'bc';
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-6854) Salted global indexes do not work for queries with uncovered columns
[
https://issues.apache.org/jira/browse/PHOENIX-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana updated PHOENIX-6854:
---
Fix Version/s: (was: 5.1.3)
> Salted global indexes do not work for queries with uncovered columns
>
>
> Key: PHOENIX-6854
> URL: https://issues.apache.org/jira/browse/PHOENIX-6854
> Project: Phoenix
> Issue Type: Bug
>Reporter: Kadir Ozdemir
>Assignee: Tanuj Khurana
>Priority: Major
> Fix For: 5.2.0
>
>
> With an index hint, global indexes can be used for queries with uncovered
> columns. However, when the data table is salted, Phoenix does not project the
> columns correctly for queries with uncovered columns, and thus the result set
> returns wrong columns. For example, the following select statement returns
> 'b' instead of 'bcde'.
>
> {code:java}
> create table T1 (id varchar not null primary key, val1 varchar, val2 varchar,
> val3 varchar) SALT_BUCKETS=4;
> upsert into T1 values ('b', 'bc', 'bcd', 'bcde');
> create index I1 on T1 (val1) include (val2);
> select /*+ INDEX(T1 I1)*/ val3 from T1 WHERE val1 = 'bc';
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Call for Presentations, Community Over Code 2023
(Note: You are receiving this because you are subscribed to the dev@ list for one or more Apache Software Foundation projects.) The Call for Presentations (CFP) for Community Over Code (formerly Apachecon) 2023 is open at https://communityovercode.org/call-for-presentations/, and will close Thu, 13 Jul 2023 23:59:59 GMT. The event will be held in Halifax, Canada, October 7-10, 2023. We welcome submissions on any topic related to the Apache Software Foundation, Apache projects, or the communities around those projects. We are specifically looking for presentations in the following catetegories: Fintech Search Big Data, Storage Big Data, Compute Internet of Things Groovy Incubator Community Data Engineering Performance Engineering Geospatial API/Microservices Frameworks Content Wrangling Tomcat and httpd Cloud and Runtime Streaming Sustainability
[jira] [Created] (PHOENIX-6951) Missing information on Index Repair Region and Time Taken to Repair
Karthik Palanisamy created PHOENIX-6951:
---
Summary: Missing information on Index Repair Region and Time Taken
to Repair
Key: PHOENIX-6951
URL: https://issues.apache.org/jira/browse/PHOENIX-6951
Project: Phoenix
Issue Type: Bug
Reporter: Karthik Palanisamy
There is no information available regarding the region(s) where the index was
repaired, nor is there any data indicating the amount of time it took to
complete the repair process, shown as empty.
Example:
{code:java}
..
2023-04-28 10:38:34,478 INFO org.apache.phoenix.index.GlobalIndexChecker: Index
row repair on region {} took {} ms.
2023-04-28 10:38:34,619 INFO org.apache.phoenix.index.GlobalIndexChecker: Index
row repair on region {} took {} ms.
..{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (PHOENIX-6932) Update LAST_DDL_TIMESTAMP for index table when add/drop/alter indexes.
[ https://issues.apache.org/jira/browse/PHOENIX-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh Shah resolved PHOENIX-6932. --- Fix Version/s: 5.2.0 Resolution: Fixed > Update LAST_DDL_TIMESTAMP for index table when add/drop/alter indexes. > -- > > Key: PHOENIX-6932 > URL: https://issues.apache.org/jira/browse/PHOENIX-6932 > Project: Phoenix > Issue Type: Sub-task >Reporter: Rushabh Shah >Assignee: Rushabh Shah >Priority: Major > Fix For: 5.2.0 > > > Currently we use LAST_DDL_TIMESTAMP only for data tables. > Create LAST_DDL_TIMESTAMP when we create an index. > Update LAST_DDL_TIMESTAMP when we alter index like disable, rebuild, > unusable, usable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
