[
https://issues.apache.org/jira/browse/BEAM-11747?focusedWorklogId=550530&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-550530
]
ASF GitHub Bot logged work on BEAM-11747:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Feb/21 02:03
Start Date: 10/Feb/21 02:03
Worklog Time Spent: 10m
Work Description: amaliujia edited a comment on pull request #13898:
URL: https://github.com/apache/beam/pull/13898#issuecomment-776378220
I am still not sure why we should reject Int64 type for UDF.
Assuming a UDF is defined as `package com.xxx.client; class name; public
Long udf(Long a)`, the code gen will generate code for UDF like `Long n =
com.xxx.client.name.udf((Long) value)`.
In this case, the value is from Row thus is compatible with ZetaSQL, the
return value is still Java object which is also be compatible with ZetaSQL.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 550530)
Time Spent: 1.5h (was: 1h 20m)
> Reject the mixed Java UDF and ZetaSQL builtin operators cases
> --------------------------------------------------------------
>
> Key: BEAM-11747
> URL: https://issues.apache.org/jira/browse/BEAM-11747
> Project: Beam
> Issue Type: Sub-task
> Components: dsl-sql-zetasql
> Reporter: Rui Wang
> Assignee: Rui Wang
> Priority: P2
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Before we have Calc splitting implemented, we can reject the mixed Java UDF
> and ZetaSQL builtin operators cases to maintain the correctness of a query.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
