[
https://issues.apache.org/jira/browse/BEAM-11747?focusedWorklogId=553259&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-553259
]
ASF GitHub Bot logged work on BEAM-11747:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/21 23:41
Start Date: 16/Feb/21 23:41
Worklog Time Spent: 10m
Work Description: amaliujia commented on pull request #13898:
URL: https://github.com/apache/beam/pull/13898#issuecomment-780189510
> The generated code prints the literal to a string and looks like this:
>
`c.output(org.apache.beam.sdk.values.Row.withSchema(outputSchema).attachValues(java.util.Arrays.asList(new
org.apache.beam.sdk.extensions.
sql.provider.UdfTestProvider.IncrementFn().increment(5L))));`
>
Based on this generated code, for a Java UDF, it's input won't lose any
precision?
Is there an example that the code generation generates code that casts input
which causes precision lose? If not there is probably no data corruption for
Java UDF.
----------------------------------------------------------------
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: 553259)
Time Spent: 3h 20m (was: 3h 10m)
> 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: 3h 20m
> 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)
