[ 
https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908780#comment-16908780
 ] 

Ivan Pavlukhin commented on IGNITE-12068:
-----------------------------------------

*Release notes*
Fixed a bug when SELECT with an equality predicate on a part of a complex 
primary key returned a single row result while multiple matching rows existed 
in the table.

> puzzling select result
> ----------------------
>
>                 Key: IGNITE-12068
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12068
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.7.5
>         Environment: System version: CentOS Linux release 7.6.1810 (Core)
> Apache Ignite version: apache-ignite-2.7.5-1.noarch
>            Reporter: JerryKwan
>            Assignee: Ivan Pavlukhin
>            Priority: Blocker
>             Fix For: 2.7.6
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> select using the first primary key only returns one record, but it should 
> return more records.
> The following is how to reproduce this problem
> 1, create a table using
> CREATE TABLE IF NOT EXISTS Person(
>  id int,
>  city_id int,
>  name varchar,
>  age int, 
>  company varchar,
>  PRIMARY KEY (id, city_id)
> );
> 2, insert some records
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4);
> INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4);
> 3, query using 'select * from Person' show all of the records, expected
> [http://www.passimage.in/i/03da31c8f23cf64580d5.png]
> 4, query using 'select * from Person where id=1', only get one record, NOT 
> expected
> [http://www.passimage.in/i/f5491491a70c5d796823.png]
> 5, query using 'select * from Person where city_id=4' get  two records, 
> expected
> [http://www.passimage.in/i/ff0ee4f5e882983d779d.png]
> Why  'select * from Person where id=1', only get one record? and how to fix 
> this? Is there any special operations/configurations to do?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to