flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2851) Merge Language-Binding into Python API and move to flink-libraries
Date Wed, 14 Oct 2015 15:06:05 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957060#comment-14957060

ASF GitHub Bot commented on FLINK-2851:

GitHub user zentol opened a pull request:


    [FLINK-2851] Move PythonAPI to flink-libraries


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zentol/flink _move_libraries

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1257
commit f9d108973c3c01f56be557cf056f193a69728e75
Author: zentol <s.motsu@web.de>
Date:   2015-10-14T14:49:31Z

    [FLINK-2851] Move PythonAPI to flink-libraries


> Merge Language-Binding into Python API and move to flink-libraries
> ------------------------------------------------------------------
>                 Key: FLINK-2851
>                 URL: https://issues.apache.org/jira/browse/FLINK-2851
>             Project: Flink
>          Issue Type: Task
>          Components: Python API
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Minor
> As discussed on the mailing list, flink-language-binding is merged into flink-python
and subsequently moved into flink-libraries. Since both these changes are of the pesky merge-conflict-creating
kind it would save me a lot of work doing both at once, instead of first merging the projects
and then waiting for a more definitive push to dissolve flink-staging.
> I'd appreciate a quick confirmation that its okay to do this so i can start rebasing
my Work in Progress.

This message was sent by Atlassian JIRA

View raw message