phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3342) ORDER BY and LIMIT+OFFSET doesnt work on second column from compound key
Date Fri, 21 Oct 2016 17:28:58 GMT

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

Hudson commented on PHOENIX-3342:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-4.8-HBase-1.2 #39 (See [https://builds.apache.org/job/Phoenix-4.8-HBase-1.2/39/])
PHOENIX-3342 ORDER BY and LIMIT+OFFSET doesnt work on second column from (ankitsinghal59:
rev b2f0c48c2ff4c425b6b192d85f218e966284152e)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java
* (edit) phoenix-core/src/test/java/org/apache/phoenix/compile/StatementHintsCompilationTest.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/iterate/BaseResultIterators.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryWithOffsetIT.java
* (edit) phoenix-core/src/test/java/org/apache/phoenix/query/QueryPlanTest.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/UnionAllIT.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/iterate/MergeSortTopNResultIterator.java


> ORDER BY and LIMIT+OFFSET doesnt work on second column from compound key
> ------------------------------------------------------------------------
>
>                 Key: PHOENIX-3342
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3342
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.1
>            Reporter: Alex Batyrshin
>            Assignee: Ankit Singhal
>             Fix For: 4.9.0, 4.8.2
>
>         Attachments: PHOENIX-3342-wip.patch, PHOENIX-3342.patch, PHOENIX-3342_v1.patch,
PHOENIX-3342_v2.patch, PHOENIX-3342_v2_4.8_branch.patch
>
>
> Here is simple test case
> {code}
> CREATE TABLE "test" (
>     col1 VARCHAR,
>     col2 VARCHAR,
>     "foo"."data" VARCHAR,
>     CONSTRAINT PK PRIMARY KEY (col1, col2)
> );
> 0: jdbc:phoenix:localhost> upsert into "test" (COL1, COL2, "data") values ('1', '1',
'd1');
> 1 row affected (0.044 seconds)
> 0: jdbc:phoenix:localhost> upsert into "test" (COL1, COL2, "data") values ('1', '2',
'd2');
> 1 row affected (0.008 seconds)
> 0: jdbc:phoenix:localhost> upsert into "test" (COL1, COL2, "data") values ('1', '3',
'd3');
> 1 row affected (0.007 seconds)
> 0: jdbc:phoenix:localhost> select * from "test" order by col2;
> +-------+-------+-------+
> | COL1  | COL2  | data  |
> +-------+-------+-------+
> | 1     | 1     | d1    |
> | 1     | 2     | d2    |
> | 1     | 3     | d3    |
> +-------+-------+-------+
> 3 rows selected (0.026 seconds)
> 0: jdbc:phoenix:localhost> select * from "test" order by col2 limit 1;
> +-------+-------+-------+
> | COL1  | COL2  | data  |
> +-------+-------+-------+
> | 1     | 1     | d1    |
> +-------+-------+-------+
> 1 row selected (0.026 seconds)
> 0: jdbc:phoenix:localhost> select * from "test" order by col2 offset 1;
> +-------+-------+-------+
> | COL1  | COL2  | data  |
> +-------+-------+-------+
> | 1     | 2     | d2    |
> | 1     | 3     | d3    |
> +-------+-------+-------+
> 2 rows selected (0.02 seconds)
> {code}
> And this query doesn't work as expected:
> {code}
> 0: jdbc:phoenix:localhost> select * from "test" order by col2 limit 1 offset 1;
> +-------+-------+-------+
> | COL1  | COL2  | data  |
> +-------+-------+-------+
> +-------+-------+-------+
> No rows selected (0.024 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message