You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by katsiapis <gi...@git.apache.org> on 2017/01/14 02:37:10 UTC
[GitHub] beam pull request #1777: [BEAM-570] Performance optimization in fileio for c...
GitHub user katsiapis opened a pull request:
https://github.com/apache/beam/pull/1777
[BEAM-570] Performance optimization in fileio for compressed sources.
- Moving from a string-based buffer to a cStringIO based on in order to help with performance of compressed sources.
- Dropping some TODOs for doing similar performance improvements in GcsIO.
- Making _CompressedFile conform to standard Python IO function names.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/katsiapis/incubator-beam io
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/1777.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 #1777
----
commit 2ee39db06ef07acfde896143a9e983ae5d1b5b13
Author: Gus Katsiapis <ka...@katsiapis-linux.mtv.corp.google.com>
Date: 2017-01-14T02:28:12Z
Moving from a string-based buffer to a cStringIO based on in order to
help with performance of compressed sources.
----
---
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.
---
[GitHub] beam pull request #1777: [BEAM-570] Performance optimization in fileio for c...
Posted by katsiapis <gi...@git.apache.org>.
Github user katsiapis closed the pull request at:
https://github.com/apache/beam/pull/1777
---
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.
---