[ https://issues.apache.org/jira/browse/BEAM-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321532#comment-15321532 ]
ASF GitHub Bot commented on BEAM-159: ------------------------------------- GitHub user robertwb opened a pull request: https://github.com/apache/incubator-beam/pull/436 Raise error rather than overwrite data when sharding is not respected This is particularly relevant when withoutSharding() is used due to [BEAM-159]. You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertwb/incubator-beam sharding Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/436.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 #436 ---- commit aa27f7fde7063a55b566b5a0a28c0b3bb667e9fe Author: Robert Bradshaw <rober...@google.com> Date: 2016-06-08T21:59:56Z Raise error rather than overwrite data when sharding is not respected This is particularly relevant when withoutSharding() is used due to [BEAM-159]. ---- > Support fixed number of shards in custom sinks > ---------------------------------------------- > > Key: BEAM-159 > URL: https://issues.apache.org/jira/browse/BEAM-159 > Project: Beam > Issue Type: Improvement > Reporter: Eugene Kirpichov > > TextIO supports .withNumShards, however custom sinks, in particular > FileBasedSinks, provide no support for controlling sharding. Some users want > this, e.g. > http://stackoverflow.com/questions/36316304/set-num-of-output-shard-in-write-tosink-in-dataflow -- This message was sent by Atlassian JIRA (v6.3.4#6332)