flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From streamnsight <...@git.apache.org>
Subject [GitHub] flink pull request: Flink dev cluster on Docker with Docker Compos...
Date Wed, 25 Mar 2015 04:07:19 GMT
GitHub user streamnsight opened a pull request:


    Flink dev cluster on Docker with Docker Compose deployment


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

    $ git pull https://github.com/streamnsight/flink master

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 #533
commit 6bbb494e0d19780c8616151704d63756eef056db
Author: streamnsight <eleroy@msn.com>
Date:   2015-03-17T03:59:51Z

    Initial commit

commit 5e3ea996bcf0506a4aef5e9bfc61d0dc86d9f471
Author: Emmanuel <emmanuel@mediumone.com>
Date:   2015-03-17T04:02:48Z

    Initial commit
    clean up

commit ba8f7b3aa40bf6cd119087902c29713e577cc9a7
Author: Emmanuel <emmanuel@mediumone.com>
Date:   2015-03-20T15:05:23Z

    Removed potentially harmful `docker rm ` clean up command (it removes
    all stopped containers)

commit f46af8c2d952b566a480c4388a410f177993fd68
Author: Robert Metzger <rmetzger@apache.org>
Date:   2015-03-24T07:52:35Z

    fix path in build.sh

commit f1b6c7e180d35dc945800dc958fd94fbca9d3ff3
Author: streamnsight <eleroy@msn.com>
Date:   2015-03-24T15:35:24Z

    Merge pull request #1 from rmetzger/minor_fix
    fix path in build.sh

commit 0975ca9775066d6608dada42c20b428179722d55
Author: Emmanuel <emmanuel@mediumone.com>
Date:   2015-03-25T04:03:55Z

    Add 'flink-contrib/docker-flink/' from commit 'f1b6c7e180d35dc945800dc958fd94fbca9d3ff3'
    git-subtree-dir: flink-contrib/docker-flink
    git-subtree-mainline: b566e484abef41d22e792dc44b9a7872064de0b3
    git-subtree-split: f1b6c7e180d35dc945800dc958fd94fbca9d3ff3


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message