[
https://issues.apache.org/jira/browse/PHOENIX-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293258#comment-17293258
]
Lars Hofhansl edited comment on PHOENIX-6400 at 3/2/21, 12:27 AM:
------------------------------------------------------------------
[~kadir] I would assume so as well. I'll try in a few.
Edit: Yes, works when v2 is included. Also the v3 column is not needed for this
to happen.
> If so, the bug is at the code that fetches the uncovered columns from the
> data table.
It's not quite that simple, because it is in the result set (the the queries in
the description). Just when we process the WHERE clause it is not there.
was (Author: lhofhansl):
[~kadir] I would assume so as well. I'll try in a few.
Edit: Yes, works when v2 is included. Also the v3 column is not needed for this
to happen.
> Local index query returns incorrect values with other columns in the WHERE
> clause
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-6400
> URL: https://issues.apache.org/jira/browse/PHOENIX-6400
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Priority: Blocker
> Fix For: 5.1.1
>
> Attachments: 6400-test-5.1.txt
>
>
> {code}
> > create table test(pk1 integer not null primary key, v1 float, v2 float, v3
> > float);
> > create local index L1 on test (v1);
> > upsert into test values(1000, 0.01, 0.1, 0.5);
> > select * from test where v1 < 0.1;
> +------+------+-----+-----+
> | PK1 | V1 | V2 | V3 |
> +------+------+-----+-----+
> | 1000 | 0.01 | 0.1 | 0.5 |
> +------+------+-----+-----+
> > select * from test where v1 < 0.1 and v2 < 10.0;
> +-----+----+----+----+
> | PK1 | V1 | V2 | V3 |
> +-----+----+----+----+
> > select /*+ NO_INDEX */ * from test where v1 < 0.1 and v2 < 10.0;
> +------+------+-----+-----+
> | PK1 | V1 | V2 | V3 |
> +------+------+-----+-----+
> | 1000 | 0.01 | 0.1 | 0.5 |
> +------+------+-----+-----+
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
