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

Hadoop QA commented on PHOENIX-3342:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12834378/PHOENIX-3342_v1.patch
  against master branch at commit 1e78d3b368b7aa8397224074f691ea2fed340e34.
  ATTACHMENT ID: 12834378

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified tests.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
43 warning messages.

    {color:red}-1 release audit{color}.  The applied patch generated 1 release 
audit warnings (more than the master's current 0 warnings).

    {color:red}-1 lineLengths{color}.  The patch introduces the following lines 
longer than 100:
    +                .executeQuery("SELECT k2 from " + tableName + " order by 
k2 desc limit " + limit + " offset " + offset);
+                    limit == null ? -1 : QueryUtil.getOffsetLimit(limit, 
offset), orderBy.getOrderByExpressions(),
+        Integer perScanLimit = !allowPageFilter || isOrdered ? null : 
QueryUtil.getOffsetLimit(limit, offset);
+                plan.getStatement().getHint(), 
QueryUtil.getOffsetLimit(plan.getLimit(), plan.getOffset()), offset);

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.UnionAllIT

Test results: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/629//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/629//artifact/patchprocess/patchReleaseAuditWarnings.txt
Javadoc warnings: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/629//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/629//console

This message is automatically generated.

> 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
>             Fix For: 4.9.0, 4.8.2
>
>         Attachments: PHOENIX-3342-wip.patch, PHOENIX-3342.patch, 
> PHOENIX-3342_v1.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)

Reply via email to