You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:57:02 UTC

[jira] [Updated] (BEAM-10595) Remove rules that not work well with Java UDF

     [ https://issues.apache.org/jira/browse/BEAM-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-10595:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Remove rules that not work well with Java UDF
> ---------------------------------------------
>
>                 Key: BEAM-10595
>                 URL: https://issues.apache.org/jira/browse/BEAM-10595
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql-zetasql
>            Reporter: Rui Wang
>            Assignee: Rui Wang
>            Priority: P2
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> In order to support Java UDF, we need both BeamZetaSqlCalcRel and BeamCalcRel. It is 
> because BeamZetaSqlCalcRel can execute ZetaSQL built-in functions while BeamCalcRel
> can execute UDFs. So during planning, we expect both Filter and Project are converted to
>  a Calc before merging with other Projec/Filter/Calc. Thus we should not add FilterCalcMergeRuleand ProjectCalcMergeRule.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)