beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [beam-site] 01/01: Prepare repository for deployment.
Date Tue, 01 May 2018 18:04:25 GMT
This is an automated email from the ASF dual-hosted git repository.

mergebot-role pushed a commit to branch asf-site
in repository

commit caae35d3898ca9c5a8768997d96efcb20112a77a
Author: Mergebot <>
AuthorDate: Tue May 1 11:04:22 2018 -0700

    Prepare repository for deployment.
 content/documentation/programming-guide/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/documentation/programming-guide/index.html b/content/documentation/programming-guide/index.html
index 8fb9cd6..2b4fa76 100644
--- a/content/documentation/programming-guide/index.html
+++ b/content/documentation/programming-guide/index.html
@@ -1705,7 +1705,7 @@ that apply to the function object itself also apply to this outer class.</li>
 <h4 id="user-code-thread-compatibility">4.3.2. Thread-compatibility</h4>
 <p>Your function object should be thread-compatible. Each instance of your function
-object is accessed by a single thread on a worker instance, unless you
+object is accessed by a single thread at a time on a worker instance, unless you
 explicitly create your own threads. Note, however, that <strong>the Beam SDKs are not
 thread-safe</strong>. If you create your own threads in your user code, you must
 provide your own synchronization. Note that static members in your function

To stop receiving notification emails like this one, please contact

View raw message