[
https://issues.apache.org/jira/browse/PHOENIX-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay wong updated PHOENIX-1064:
------------------------------
Description:
1. jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder;
| PK1 | COL1 | COL2 |
| row1 | 2 | 3 |
| row2 | 3 | 4 |
| row3 | 4 | 5 |
| row4 | 5 | null |
| row5 | 5 | null |
2.jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder order by col2;
| PK1 | COL1 | COL2 |
| row4 | 5 | null |
| row5 | 5 | null |
| row1 | 2 | 3 |
| row2 | 3 | 4 |
| row3 | 4 | 5 |
3. jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder order by col2 desc;
| PK1 | COL1 | COL2 |
| row4 | 5 | null |
| row5 | 5 | null |
| row3 | 4 | 5 |
| row2 | 3 | 4 |
| row1 | 2 | 3 |
I think it will be at last when the column is null as default
As mysql or oracle DB is at last.
It is More in line with normal logic of thinking.
was:
1. jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder;
| PK1 | COL1 | COL2 |
| row1 | 2 | 3 |
| row2 | 3 | 4 |
| row3 | 4 | 5 |
| row4 | 5 | null |
| row5 | 5 | null |
2.jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder order by col2;
| PK1 | COL1 | COL2 |
| row4 | 5 | null |
| row5 | 5 | null |
| row1 | 2 | 3 |
| row2 | 3 | 4 |
| row3 | 4 | 5 |
3. jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder order by col2 desc;
| PK1 | COL1 | COL2 |
| row4 | 5 | null |
| row5 | 5 | null |
| row3 | 4 | 5 |
| row2 | 3 | 4 |
| row1 | 2 | 3 |
I think it will be at last when the column is null as default
As mysql or oracle DB is at last.
It is More in line with normal logic of thinking.
> In order by case, I think nulls last will be default
> ----------------------------------------------------
>
> Key: PHOENIX-1064
> URL: https://issues.apache.org/jira/browse/PHOENIX-1064
> Project: Phoenix
> Issue Type: New Feature
> Reporter: jay wong
>
> 1. jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder;
> | PK1 | COL1 | COL2 |
> | row1 | 2 | 3 |
> | row2 | 3 | 4 |
> | row3 | 4 | 5 |
> | row4 | 5 | null |
> | row5 | 5 | null |
> 2.jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder order by col2;
> | PK1 | COL1 | COL2 |
> | row4 | 5 | null |
> | row5 | 5 | null |
> | row1 | 2 | 3 |
> | row2 | 3 | 4 |
> | row3 | 4 | 5 |
> 3. jdbc:phoenix:ip:/hbase-phoenix-l> select * from testorder order by col2
> desc;
> | PK1 | COL1 | COL2 |
> | row4 | 5 | null |
> | row5 | 5 | null |
> | row3 | 4 | 5 |
> | row2 | 3 | 4 |
> | row1 | 2 | 3 |
> I think it will be at last when the column is null as default
> As mysql or oracle DB is at last.
> It is More in line with normal logic of thinking.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
