This is an automated email from the ASF dual-hosted git repository.
yhu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/master by this push:
new bcdac047062 Update test-your-pipeline.md (#30328)
bcdac047062 is described below
commit bcdac04706247fe96bbdb53cbef96af4ae9e0aad
Author: Dan Ellis <dan.el...@gmail.com>
AuthorDate: Thu Feb 15 10:19:59 2024 -0500
Update test-your-pipeline.md (#30328)
The spurious extra "-" between "debugging" and "failed" drastically changes
the grammar of the sentence and makes it hard to parse.
---
.../www/site/content/en/documentation/pipelines/test-your-pipeline.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/website/www/site/content/en/documentation/pipelines/test-your-pipeline.md
b/website/www/site/content/en/documentation/pipelines/test-your-pipeline.md
index 107ec2a5524..1ab47dd540a 100644
--- a/website/www/site/content/en/documentation/pipelines/test-your-pipeline.md
+++ b/website/www/site/content/en/documentation/pipelines/test-your-pipeline.md
@@ -18,7 +18,7 @@ limitations under the License.
{{< toc >}}
-Testing your pipeline is a particularly important step in developing an
effective data processing solution. The indirect nature of the Beam model, in
which your user code constructs a pipeline graph to be executed remotely, can
make debugging-failed runs a non-trivial task. Often it is faster and simpler
to perform local unit testing on your pipeline code than to debug a pipeline's
remote execution.
+Testing your pipeline is a particularly important step in developing an
effective data processing solution. The indirect nature of the Beam model, in
which your user code constructs a pipeline graph to be executed remotely, can
make debugging failed runs a non-trivial task. Often it is faster and simpler
to perform local unit testing on your pipeline code than to debug a pipeline's
remote execution.
Before running your pipeline on the runner of your choice, unit testing your
pipeline code locally is often the best way to identify and fix bugs in your
pipeline code. Unit testing your pipeline locally also allows you to use your
familiar/favorite local debugging tools.
