GitHub user dhalperi opened a pull request:
https://github.com/apache/beam/pull/2887
[BEAM-59] Swap IOChannel to FileSystems finishing touches
All these are small.
After this, all I have left is BigQuery.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dhalperi/beam iocf-die-die-die
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2887.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2887
----
commit 62643043f785f75e7fc0b25e8fcf876b5cb89e63
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T00:50:20Z
AvroIOTest: stop using IOChannelUtils, remove invalid test
commit 119d0b962590bc9e7fd83937b3103ed1bc3d9384
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T00:55:32Z
DataflowRunner: switch from IOChannels to FileSystems for creating files
commit 42d264877648b34f6034549e746f7a3eb69b38d4
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T01:01:29Z
DataflowPipelineOptions: use FileSystems, not IOChannelUtils, to resolve
staging location
commit 4327af07e99a1d3f080b47d449302cfb729f6197
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T01:02:42Z
Stop registering IOChannelFactories in SDK harness, runners, tests
commit 0cf14b87569e91f8c317ae3130d8dc4ee9da91df
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T01:11:34Z
WriteWithShardingFactoryTest: switch to FileSystems
commit e8d78653afc8fc7bebf0da95103e7fee136279c4
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T01:18:52Z
ReadTranslator: remove outdated comment
commit 91d5903c26044904c99cc4d1e0f7a39a98a90be6
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T02:34:04Z
FileSystems: add match(String) for single spec
commit 42ad4bcf8bed7843aa7478062534c420d56cfa26
Author: Dan Halperin <[email protected]>
Date: 2017-05-04T02:34:25Z
TFRecordIO: switch to FileSystems from IOChannelUtils
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
