You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "sunjincheng (JIRA)" <ji...@apache.org> on 2019/06/14 09:10:00 UTC
[jira] [Closed] (FLINK-12803) Correct the package name for python
API
[ https://issues.apache.org/jira/browse/FLINK-12803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sunjincheng closed FLINK-12803.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed in master: e6ba90c311f41f341f96cfeda5963e65b9b71fd0
> Correct the package name for python API
> ---------------------------------------
>
> Key: FLINK-12803
> URL: https://issues.apache.org/jira/browse/FLINK-12803
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Affects Versions: 1.9.0
> Reporter: sunjincheng
> Assignee: Dian Fu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the package name of flink APIs should cantians the language name, such as:
> * flink-java -> org.apache.flink.api.java
> * flink-scala -> org.apache.flink.api.scala
> So I think we should follow the pattern of API package name and correct the current python API package name for `flink-python`. But for long-term goal, the flink API package name should be:
> * org.apache.flink.api.common.
> * org.apache.flink.api.common.python.
> * org.apache.flink.api.datastream.
> * org.apache.flink.api.datastream.scala.
> * org.apache.flink.api.datastream.python.
> * org.apache.flink.api.table.
> * org.apache.flink.api.table.scala.
> * org.apache.flink.api.table.python.
> So, in this JIRA, we should correct the package name from `org.apache.flink.python` -------> `org.apache.flink.api.table.python`
> What do you think?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)