You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Hequn Cheng (Jira)" <ji...@apache.org> on 2019/09/23 12:14:00 UTC
[jira] [Closed] (FLINK-14015) Introduce
PythonScalarFunctionOperator as a standalone StreamOperator for Python
ScalarFunction execution
[ https://issues.apache.org/jira/browse/FLINK-14015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hequn Cheng closed FLINK-14015.
-------------------------------
Resolution: Resolved
> Introduce PythonScalarFunctionOperator as a standalone StreamOperator for Python ScalarFunction execution
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-14015
> URL: https://issues.apache.org/jira/browse/FLINK-14015
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Reporter: Dian Fu
> Assignee: Dian Fu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> PythonScalarFunctionOperator is a standalone StreamOperator and it doesn’t need to how the Python ScalarFunctions are executed which is the responsibility of PythonScalarFunctionRunner:
> # It is a StreamOperator which employs PythonScalarFunctionRunner for Python ScalarFunction execution
> # It sends input elements to PythonScalarFunctionRunner, fetches the execution results, constructs the result rows and sends them to the downstream operator
> # It should handle the checkpoint and watermark properly
--
This message was sent by Atlassian Jira
(v8.3.4#803005)