You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sedona.apache.org by "Kengo Seki (Jira)" <ji...@apache.org> on 2022/08/06 13:27:00 UTC

[jira] [Created] (SEDONA-137) Fix ST_Buffer for Flink to work

Kengo Seki created SEDONA-137:
---------------------------------

             Summary: Fix ST_Buffer for Flink to work
                 Key: SEDONA-137
                 URL: https://issues.apache.org/jira/browse/SEDONA-137
             Project: Apache Sedona
          Issue Type: Bug
            Reporter: Kengo Seki


I tried to use the {{ST_Buffer}} function on Flink, but came across the following error.

{code}
org.apache.flink.client.program.ProgramInvocationException: The main method caused an error: SQL validation failed. An error occurred in the type inference logic of function 'ST_Buffer'.

...

Caused by: org.apache.flink.table.api.ValidationException: SQL validation failed. An error occurred in the type inference logic of function 'ST_Buffer'.

...

Caused by: org.apache.flink.table.api.ValidationException: An error occurred in the type inference logic of function 'ST_Buffer'.

...

Caused by: org.apache.flink.table.api.ValidationException: Could not extract a valid type inference for function class 'org.apache.sedona.flink.expressions.Functions$ST_Buffer'. Please check for implementation mistakes and/or provide a corresponding hint.

...

Caused by: org.apache.flink.table.api.ValidationException: Error in extracting a signature to output mapping.

...

Caused by: org.apache.flink.table.api.ValidationException: Unable to extract a type inference from method:

...

Caused by: org.apache.flink.table.api.ValidationException: Could not extract a data type from 'class java.lang.Object' in parameter 0 of method 'eval' in class 'org.apache.sedona.flink.expressions.Functions$ST_Buffer'. Please pass the required data type manually or allow RAW types.
{code}

It seems to be caused by the lack of {{@DataTypeHint}} for the first parameter of {{ST_Buffer.eval}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)