This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push: new 0a47b92 Publishing website 2019/09/16 15:55:04 at commit d93e4e0 0a47b92 is described below commit 0a47b9221378a5bfc7b8b5cc33660fc38def79b2 Author: jenkins <bui...@apache.org> AuthorDate: Mon Sep 16 15:55:04 2019 +0000 Publishing website 2019/09/16 15:55:04 at commit d93e4e0 --- website/generated-content/documentation/execution-model/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/generated-content/documentation/execution-model/index.html b/website/generated-content/documentation/execution-model/index.html index e9db33f..4d52a9a 100644 --- a/website/generated-content/documentation/execution-model/index.html +++ b/website/generated-content/documentation/execution-model/index.html @@ -502,7 +502,7 @@ and for other reasons such as persistence.</p> <p>A runner may decide to transfer elements between transforms in a variety of ways, such as:</p> -<ol> +<ul> <li>Routing elements to a worker for processing as part of a grouping operation. This may involve serializing elements and grouping or sorting them by their key.</li> @@ -514,7 +514,7 @@ the <code class="highlighter-rouge">ParDo</code>.</li> <li>Passing elements between transforms that are running on the same worker. This may allow the runner to avoid serializing elements; instead, the runner can just pass the elements in memory.</li> -</ol> +</ul> <p>Some situations where the runner may serialize and persist elements are:</p>