[
https://issues.apache.org/jira/browse/HIVE-14382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410841#comment-15410841
]
Lefty Leverenz commented on HIVE-14382:
---------------------------------------
[~dmtolpeko], the second example in the doc ([http://hplsql.org/for-range])
still shows upper_bound before lower_bound:
{code}
FOR i IN REVERSE 10..1 LOOP
-- i will have values: 10, 9, 8, 7, 6, 5, 4, 3, 1, 1
END LOOP;
{code}
> Improve the Functionality of Reverse FOR Statement
> ---------------------------------------------------
>
> Key: HIVE-14382
> URL: https://issues.apache.org/jira/browse/HIVE-14382
> Project: Hive
> Issue Type: Improvement
> Components: hpl/sql
> Reporter: Akash Sethi
> Assignee: Akash Sethi
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: HIVE-14382.1-branch-2.1.patch, HIVE-14382.1.patch
>
> 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)
