[
https://issues.apache.org/jira/browse/TAJO-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996310#comment-14996310
]
Hudson commented on TAJO-1972:
------------------------------
FAILURE: Integrated in Tajo-master-CODEGEN-build #587 (See
[https://builds.apache.org/job/Tajo-master-CODEGEN-build/587/])
TAJO-1972: Invalid sort order with NULLS FIRST|LAST. (jihoonson: rev
46bc8bf7901ca124c76a6c1cfb0c3b161c8ad7d2)
*
tajo-storage/tajo-storage-common/src/test/java/org/apache/tajo/storage/TestTupleComparator.java
* tajo-plan/src/main/java/org/apache/tajo/plan/logical/SortNode.java
*
tajo-storage/tajo-storage-common/src/main/java/org/apache/tajo/storage/BaseTupleComparator.java
* CHANGES
> Invalid sort order with NULLS FIRST|LAST
> -----------------------------------------
>
> Key: TAJO-1972
> URL: https://issues.apache.org/jira/browse/TAJO-1972
> Project: Tajo
> Issue Type: Bug
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Critical
> Fix For: 0.12.0, 0.11.1
>
>
> Currently, the order of nulls is affected by the sort order (asc and desc),
> but should not. Here is the example of pgsql's behaviour.
> {noformat}
> postgres=# select * from test;
> id | name
> ----+-------
> 0 | test1
> 1 |
> | test2
> (3 rows)
> postgres=# select * from test order by id asc nulls first;
> id | name
> ----+-------
> | test2
> 0 | test1
> 1 |
> (3 rows)
> postgres=# select * from test order by id desc nulls first;
> id | name
> ----+-------
> | test2
> 1 |
> 0 | test1
> (3 rows)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
