[
https://issues.apache.org/jira/browse/HIVE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856638#action_12856638
]
Edward Capriolo commented on HIVE-1304:
---------------------------------------
Can we work on... https://issues.apache.org/jira/browse/HIVE-1265..first.
As of now commits on UDF's is a major pain. Two or three times already I had
had to regenerate UDFs because someone else touched the FunctionRegistry. I
have had two or three waves of UDF's I want to commit ReflectionUDF, MathUDF,
EncryptionUDF but something else sneaks in and I have to regenerate. It is a
major pain.
> add row_sequence UDF
> --------------------
>
> Key: HIVE-1304
> URL: https://issues.apache.org/jira/browse/HIVE-1304
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Metastore
> Affects Versions: 0.6.0
> Reporter: John Sichi
> Assignee: John Sichi
> Fix For: 0.6.0
>
> Attachments: HIVE-1304.1.patch
>
>
> This is a poor man's answer to the standard analytic function row_number();
> it assigns a sequence of numbers to rows, starting from 1.
> I'm calling it row_sequence() to distinguish it from the real analytic
> function, so that once we add support for those, there won't be any conflict
> with the existing UDF.
> The problem with this UDF approach is that there are no guarantees about
> ordering in SQL processing internals, so use with caution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
