[
https://issues.apache.org/jira/browse/BEAM-6713?focusedWorklogId=202852&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-202852
]
ASF GitHub Bot logged work on BEAM-6713:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Feb/19 20:16
Start Date: 22/Feb/19 20:16
Worklog Time Spent: 10m
Work Description: kyle-winkelman commented on issue #7893: [BEAM-6713]
Add withMaxNumWritersPerBundle from WriteFiles to FileIO …
URL: https://github.com/apache/beam/pull/7893#issuecomment-466532568
Should this also be added to AvroIO and TFRecordIO? Or conversely removed
from TextIO?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 202852)
Time Spent: 40m (was: 0.5h)
> FileIO and TextIO unable to alter WriteFiles maxNumWritersPerBundle
> -------------------------------------------------------------------
>
> Key: BEAM-6713
> URL: https://issues.apache.org/jira/browse/BEAM-6713
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Kyle Winkelman
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When attempting to run a batch workflow with a FileIO.write() I was getting
> job failures due to WriteFiles.DEFAULT_MAX_NUM_WRITERS_PER_BUNDLE causing a
> significant amount of data to be shuffled. My issues would be solved by
> increasing this and luckily WriteFiles already has withMaxNumWritersPerBundle
> but unfortunately FileIO and TextIO do not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
