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

Hudson commented on HIVE-3490:
------------------------------

Integrated in Hive-trunk-hadoop2 #138 (See 
[https://builds.apache.org/job/Hive-trunk-hadoop2/138/])
    HIVE-3490 Implement * or a.* for arguments to UDFs
(Navis via namit) (Revision 1452189)

     Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1452189
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/IdentifiersParser.g
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
* 
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/TypeCheckProcFactory.java
* 
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/ExprNodeColumnListDesc.java
* /hive/trunk/ql/src/test/queries/clientpositive/allcolref_in_udf.q
* /hive/trunk/ql/src/test/results/clientpositive/allcolref_in_udf.q.out

                
> Implement * or a.* for arguments to UDFs
> ----------------------------------------
>
>                 Key: HIVE-3490
>                 URL: https://issues.apache.org/jira/browse/HIVE-3490
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor, UDF
>            Reporter: Adam Kramer
>            Assignee: Navis
>             Fix For: 0.11.0
>
>         Attachments: HIVE-3490.D8889.1.patch, HIVE-3490.D8889.2.patch
>
>
> For a random UDF, we should be able to use * or a.* to refer to "all of the 
> columns in their natural order." This is not currently implemented.
> I'm reporting this as a bug because it is a manner in which Hive is 
> inconsistent with the SQL spec, and because Hive claims to implement *.
> hive> select all_non_null(a.*) from table a where a.ds='2012-09-01';
> FAILED: ParseException line 1:25 mismatched input '*' expecting Identifier 
> near '.' in expression specification

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to