You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Dmitry Tolpeko (JIRA)" <ji...@apache.org> on 2016/07/29 12:58:20 UTC

[jira] [Commented] (HIVE-14382) Improve the Functionality of Reverse FOR Statement

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

Dmitry Tolpeko commented on HIVE-14382:
---------------------------------------

Akash, right now this functionality is part of Hive HPL/SQL component, see docs: http://hplsql.org/for-range

> Improve the Functionality of Reverse  FOR Statement
> ---------------------------------------------------
>
>                 Key: HIVE-14382
>                 URL: https://issues.apache.org/jira/browse/HIVE-14382
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Akash Sethi
>            Assignee: Akash Sethi
>            Priority: Minor
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> According to SQL Standards, Reverse FOR Statement should be like this:-
> FOR index IN Optional[Reverse] Lower_Bound Upper_Bound
> but in hive it is like this :- 
> FOR index IN Optional[Reverse]  Upper_Bound Lower_Bound
> so i m just trying to improve the functionality for Reverse FOR Statement
> REFERNCES :- https://docs.oracle.com/cloud/latest/db112/LNPLS/for_loop_statement.htm#LNPLS1536



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