Repository: beam-site Updated Branches: refs/heads/asf-site 49ffb13f0 -> 64b7bca76
[BEAM-1272] Align the naming of "generateInitialSplits" and "splitIntoBundles" to better reflect their intention Project: http://git-wip-us.apache.org/repos/asf/beam-site/repo Commit: http://git-wip-us.apache.org/repos/asf/beam-site/commit/a259cf58 Tree: http://git-wip-us.apache.org/repos/asf/beam-site/tree/a259cf58 Diff: http://git-wip-us.apache.org/repos/asf/beam-site/diff/a259cf58 Branch: refs/heads/asf-site Commit: a259cf586568609275ea634ebd98ef8ca86d65b6 Parents: 49ffb13 Author: echauchot <[email protected]> Authored: Thu Apr 13 10:50:30 2017 +0200 Committer: Dan Halperin <[email protected]> Committed: Tue Apr 18 12:02:22 2017 -0700 ---------------------------------------------------------------------- src/contribute/ptransform-style-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/beam-site/blob/a259cf58/src/contribute/ptransform-style-guide.md ---------------------------------------------------------------------- diff --git a/src/contribute/ptransform-style-guide.md b/src/contribute/ptransform-style-guide.md index 92e9775..34f7c45 100644 --- a/src/contribute/ptransform-style-guide.md +++ b/src/contribute/ptransform-style-guide.md @@ -160,7 +160,7 @@ Data processing is tricky, full of corner cases, and difficult to debug, because * Third-party APIs failing * Third-party APIs providing wildly inaccurate information * Leaks of `Closeable`/`AutoCloseable` resources in failure cases - * Common corner cases when developing sources: complicated arithmetic in `BoundedSource.splitIntoBundles` (e.g. splitting key or offset ranges), iteration over empty data sources or composite data sources that have some empty components. + * Common corner cases when developing sources: complicated arithmetic in `BoundedSource.split` (e.g. splitting key or offset ranges), iteration over empty data sources or composite data sources that have some empty components. * Mock out the interactions with third-party systems, or better, use ["fake"](http://martinfowler.com/articles/mocksArentStubs.html) implementations when available. Make sure that the mocked-out interactions are representative of all interesting cases of the actual behavior of these systems. * To unit test `DoFn`s, `CombineFn`s, and `BoundedSource`s, consider using `DoFnTester`, `CombineFnTester`, and `SourceTestUtils` respectively which can exercise the code in non-trivial ways to flesh out potential bugs. * For transforms that work over unbounded collections, test their behavior in the presence of late or out-of-order data using `TestStream`.
