You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/07/21 07:53:00 UTC

[jira] [Updated] (FLINK-9430) Support Casting of Object to Primitive types for Flink SQL UDF

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

ASF GitHub Bot updated FLINK-9430:
----------------------------------
    Labels: pull-request-available  (was: )

> Support Casting of Object to Primitive types for Flink SQL UDF
> --------------------------------------------------------------
>
>                 Key: FLINK-9430
>                 URL: https://issues.apache.org/jira/browse/FLINK-9430
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / API
>            Reporter: Shuyi Chen
>            Priority: Major
>              Labels: pull-request-available
>
> We want to add a SQL UDF to access specific element in a JSON string using JSON path. However, the JSON element can be of different types, e.g. Int, Float, Double, String, Boolean and etc.. Since return type is not part of the method signature, we can not use overload. So we will end up writing a UDF for each type, e.g. GetFloatFromJSON, GetIntFromJSON and etc., which has a lot of duplication. 
> One way to unify all these UDF functions is to implement one UDF and return java.lang.Object, and in the SQL statement, use CAST AS to cast the returned Object into the correct type. Below is an example:
>  
> {code:java}
> object JsonPathUDF extends ScalarFunction {
>  def eval(jsonStr: String, path: String): Object = {
>    JSONParser.parse(jsonStr).read(path)
>  }
> }{code}
> {code:java}
>  SELECT CAST(jsonpath(json, "$.store.book.title") AS VARCHAR(32)) as bookTitle FROM table1{code}
> The current Flink SQL cast implementation does not support casting from GenericTypeInfo<java.lang.Object> to another type, I have already got a local branch to fix this. Please comment if there are alternatives to the problem above.



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