[
https://issues.apache.org/jira/browse/HIVE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459968#comment-13459968
]
Adam Kramer commented on HIVE-3491:
-----------------------------------
These aren't "functions," they're classes and methods -- and it is entirely
reasonable from a programming standpoint to have classes be created or
instantiated with some amount of context.
We already have certain functions fail in certain ways because "strict mode" is
not set to on, for example -- this task is to let "User-Defined" functions do
this, too.
Also, from an underpinnings standpoint, it is entirely reasonable for a job
running on a mapreduce node to pass random set variables from the client to the
nodes.
And once again, there ARE cases in which the user cannot easily pass the column
names in, as mentioned, when using an asterisk to sweep all of the columns.
> Expose column names to UDFs
> ---------------------------
>
> Key: HIVE-3491
> URL: https://issues.apache.org/jira/browse/HIVE-3491
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor, UDF
> Reporter: Adam Kramer
>
> If I run
> SELECT MY_FUNC(a.foo, b.bar) FROM baz1 a JOIN baz2 b;
> ...the parsed query structure (i.e., that "foo" and "bar" are the name of the
> columns) should be available to the UDF in some manner.
--
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
