You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Xu Mingmin (JIRA)" <ji...@apache.org> on 2018/11/01 21:26:00 UTC

[jira] [Closed] (BEAM-5921) [SQL] Support Joda types for UDF arguments

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

Xu Mingmin closed BEAM-5921.
----------------------------
       Resolution: Done
    Fix Version/s: 2.9.0

> [SQL] Support Joda types for UDF arguments
> ------------------------------------------
>
>                 Key: BEAM-5921
>                 URL: https://issues.apache.org/jira/browse/BEAM-5921
>             Project: Beam
>          Issue Type: Bug
>          Components: dsl-sql
>            Reporter: Anton Kedin
>            Assignee: Xu Mingmin
>            Priority: Major
>             Fix For: 2.9.0
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> We call ScalarFunctionImpl.create() to register a UDF with Calcite schema in BeamSqlEnv. Internally it uses Calcite's internal mapping (JavaToSqlTypeConversionRules) to map Java types to SQL types to create a function signature that gets registered in the schema. Problem is that this logic is not extensible and doesn't include Joda types support (maybe others as well).
> We can work around this by constructing our own subclass of Function that gets registered in the schema instead of calling ScalarFunctionImpl.create(). This logic can use our own custom mapping (or fall back to Calcite implementation if needed).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)