You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2019/02/27 14:06:00 UTC

[jira] [Closed] (FLINK-11752) Move flink-python to opt

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

Ufuk Celebi closed FLINK-11752.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

> Move flink-python to opt
> ------------------------
>
>                 Key: FLINK-11752
>                 URL: https://issues.apache.org/jira/browse/FLINK-11752
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Python, Build System
>    Affects Versions: 1.7.2
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed on the [dev mailing list|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Move-flink-python-to-opt-td27347.html], we should move flink-python to opt instead of having it in lib by default.
> The streaming counter part (flink-streaming-python) is only as part of opt already.
> I think we don't have many users of the Python batch API and this will make the streaming/batch experience more consistent and would result in a cleaner default classpath. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)