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

Hudson commented on PHOENIX-2067:
---------------------------------

SUCCESS: Integrated in Phoenix-master #841 (See 
[https://builds.apache.org/job/Phoenix-master/841/])
PHOENIX-2067 Sort order incorrect for variable length DESC columns - ARRAY 
(ramkrishna: rev 33d60506c5f2d4408a1df79f278d7a45d3401a27)
* 
phoenix-core/src/test/java/org/apache/phoenix/expression/ArrayAppendFunctionTest.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/types/PArrayDataType.java
* 
phoenix-core/src/test/java/org/apache/phoenix/schema/types/PDataTypeForArraysTest.java
* 
phoenix-core/src/test/java/org/apache/phoenix/expression/ArrayPrependFunctionTest.java
* 
phoenix-core/src/test/java/org/apache/phoenix/expression/ArrayConcatFunctionTest.java


> Sort order incorrect for variable length DESC columns
> -----------------------------------------------------
>
>                 Key: PHOENIX-2067
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2067
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.4.0
>         Environment: HBase 0.98.6-cdh5.3.0
> jdk1.7.0_67 x64
> CentOS release 6.4 (2.6.32-358.el6.x86_64)
>            Reporter: Mykola Komarnytskyy
>            Assignee: James Taylor
>             Fix For: 4.5.0
>
>         Attachments: PHOENIX-2067-tests.patch, PHOENIX-2067-tests2.patch, 
> PHOENIX-2067_addendum.patch, PHOENIX-2067_array_addendum.patch, 
> PHOENIX-2067_array_addendum_v2.patch, PHOENIX-2067_v1.patch, 
> PHOENIX-2067_v2.patch, PHOENIX-2067_v3.patch
>
>
> Steps to reproduce:
> 1. Create a table: 
> CREATE TABLE mytable (id BIGINT not null PRIMARY KEY, timestamp BIGINT, 
> log_message varchar) IMMUTABLE_ROWS=true, SALT_BUCKETS=16;
> 2. Create two indexes:
> CREATE INDEX mytable_index_search ON mytable(timestamp,id) INCLUDE 
> (log_message) SALT_BUCKETS=16;
> CREATE INDEX mytable_index_search_desc ON mytable(timestamp DESC,id DESC) 
> INCLUDE (log_message) SALT_BUCKETS=16;
> 3. Upsert values:
> UPSERT INTO mytable VALUES(1, 1434983826018, 'message1');
> UPSERT INTO mytable VALUES(2, 1434983826100, 'message2');
> UPSERT INTO mytable VALUES(3, 1434983826101, 'message3');
> UPSERT INTO mytable VALUES(4, 1434983826202, 'message4');
> 4. Sort DESC by timestamp:
> select timestamp,id,log_message from mytable ORDER BY timestamp DESC;
> Failure: data is sorted incorrectly. In case when we have two longs which  
> are different only by last two digits (e.g. 1434983826155, 1434983826100)  
> and one of the long ends with '00' we receive incorrect order. 
> Sorting result:
> 1434983826202
> 1434983826100
> 1434983826101
> 1434983826018



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

Reply via email to