You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2015/11/09 11:10:10 UTC

[jira] [Resolved] (TAJO-1972) Invalid sort order with NULLS FIRST|LAST

     [ https://issues.apache.org/jira/browse/TAJO-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jihoon Son resolved TAJO-1972.
------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Committed to master and 0.11.1

> 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)