You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dian Fu (Jira)" <ji...@apache.org> on 2020/02/17 08:19:00 UTC
[jira] [Closed] (FLINK-16109) Move the Python scalar operators and
table operators to separate package
[ https://issues.apache.org/jira/browse/FLINK-16109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dian Fu closed FLINK-16109.
---------------------------
Resolution: Resolved
Merged to master via 85794f7a0c047bba67d9b7e52233164db1793549.
> Move the Python scalar operators and table operators to separate package
> ------------------------------------------------------------------------
>
> Key: FLINK-16109
> URL: https://issues.apache.org/jira/browse/FLINK-16109
> Project: Flink
> Issue Type: Improvement
> Components: API / Python
> Reporter: Dian Fu
> Assignee: Huang Xingbo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently both the Python scalar operators and table operators are under the same package org.apache.flink.table.runtime.operators.python. There are already many operators under this package. After introducing the aggregate function support and Vectorized Python function support in the future, there will be more and more operators under the same package.
> We could improve it by the following package structure: org.apache.flink.table.runtime.operators.python.scalar
> org.apache.flink.table.runtime.operators.python.table
> org.apache.flink.table.runtime.operators.python.aggregate (in the future)
> org.apache.flink.table.runtime.operators.python.scalar.arrow (in the future)
> As these classes are internal, it's safe to do so and there are no backwards compatibility issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)