[
https://issues.apache.org/jira/browse/HIVE-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153197#comment-16153197
]
Dmitry Tolpeko commented on HIVE-17027:
---------------------------------------
Actually HPL already parses double quoted strings as identifiers, I will change
the logic to treat them as strings depending on the context, for example, in
assignment expressions that are not part of SQL statements where conflict with
column names is possible; and when there is no previously declared
double-quoted variable etc.
> HPL/SQL requires single quotes for string literals, resulting in surprising
> behavior
> ------------------------------------------------------------------------------------
>
> Key: HIVE-17027
> URL: https://issues.apache.org/jira/browse/HIVE-17027
> Project: Hive
> Issue Type: Bug
> Components: hpl/sql
> Reporter: Carter Shanklin
> Assignee: Dmitry Tolpeko
> Priority: Critical
>
> This bug is part of a series of issues and surprising behavior I encountered
> writing a reporting script that would aggregate values and give rows
> different classifications based on an the aggregate. Addressing some or all
> of these issues would make HPL/SQL more accessible to newcomers.
> Consider this script:
> {code}
> CREATE FUNCTION test1()
> RETURNS STRING
> DECLARE
> VAR ret string;
> BEGIN
> ret := 'VALUE IS SET';
> print(ret);
> END;
> CREATE FUNCTION test2()
> RETURNS STRING
> DECLARE
> VAR ret string;
> BEGIN
> ret := "VALUE IS SET";
> print(ret);
> END;
> test1();
> test2();
> {code}
> The output of this script is:
> VALUE IS SET
> ret
> Hive accepts both quoting styles. It would be better if HPL/SQL did as well,
> or threw an error for th
> e unsupported style.
> Version = 3.0.0-SNAPSHOT r71f52d8ad512904b3f2c4f04fe39a33f2834f1f2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
