beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dhalperi <>
Subject [GitHub] beam pull request #2814: [BEAM-59] Minor changes that can be separated out f...
Date Tue, 02 May 2017 01:56:06 GMT
GitHub user dhalperi opened a pull request:

    [BEAM-59] Minor changes that can be separated out from big PR

    All these are minor changes, correct at HEAD, and standalone from #2779

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

    $ git pull test-cleanup

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 #2814
commit dbfe24b408c0ebeb003804676484214640ea10df
Author: Dan Halperin <>
Date:   2017-05-02T01:43:23Z

    [BEAM-59] Core tests: stop using gs:// paths
    Local filesystem is just as good an example, and in the
    future these may break because GCS filesystem is not present
    in sdks/java/core.

commit 6b0fa09eb45dfe51d9d93112deea79ff6578e167
Author: Dan Halperin <>
Date:   2017-05-02T01:46:24Z

    [BEAM-59] TFRecordIOTest: cleanup
    1. Shrink file size slightly to reduce test time.
    2. Switch from relative to absolute local file paths, because in the future
       this distinction will matter.

commit 7a02eab9f70f962499101c039a78bcafc2725d3e
Author: Dan Halperin <>
Date:   2017-05-02T01:49:28Z

    [BEAM-59] DataflowRunnerTests: configure FileSystems in test
    This enables the test to use gs:// URIs with the FileSystems API

commit 5ac3cff9b774d1e0c3ce7ee91bfd8aa23cd2dc27
Author: Dan Halperin <>
Date:   2017-05-02T01:54:40Z

    [BEAM-59] AvroIOTest: use absolute paths for display data
    This is future-proofing against eventual conversion to FileSystems API in which all paths
    are absolute


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 or file a JIRA ticket
with INFRA.

View raw message