hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <>
Subject [jira] [Commented] (HIVE-12994) Implement support for NULLS FIRST/NULLS LAST
Date Mon, 29 Feb 2016 23:45:18 GMT


Ashutosh Chauhan commented on HIVE-12994:

Are we reserving _nulls_ and _last_ as keyword in grammar with this change ? If not, can you
add test case like
create table nulls (last int);
to ensure in future this doesnt get impacted?

> Implement support for NULLS FIRST/NULLS LAST
> --------------------------------------------
>                 Key: HIVE-12994
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: CBO, Parser, Serializers/Deserializers
>    Affects Versions: 2.1.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-12994.01.patch, HIVE-12994.02.patch, HIVE-12994.03.patch, HIVE-12994.04.patch,
HIVE-12994.05.patch, HIVE-12994.06.patch, HIVE-12994.06.patch, HIVE-12994.07.patch, HIVE-12994.08.patch,
HIVE-12994.09.patch, HIVE-12994.10.patch, HIVE-12994.11.patch, HIVE-12994.patch
> From SQL:2003, the NULLS FIRST and NULLS LAST options can be used to determine whether
nulls appear before or after non-null data values when the ORDER BY clause is used.
> SQL standard does not specify the behavior by default. Currently in Hive, null values
sort as if lower than any non-null value; that is, NULLS FIRST is the default for ASC order,
and NULLS LAST for DESC order.

This message was sent by Atlassian JIRA

View raw message