This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
The following commit(s) were added to refs/heads/mergebot by this push:
new 46ac20f [BEAM-4177] Clarify thread contraint in Programming Guide
4.3.2
new 454a926 This closes #430
46ac20f is described below
commit 46ac20fb5ab53fd1bc15a7d76b2e88ce0f20e1d3
Author: John MacMillan <[email protected]>
AuthorDate: Thu Apr 26 10:32:50 2018 -0400
[BEAM-4177] Clarify thread contraint in Programming Guide 4.3.2
As checked on the dev mailing list, the instance will only be active on a
single thread at a time, not the more restrictive single thread ever.
Without clarification, some developers may conservatively assume the
constraint
is more restrictive than it really is.
---
src/documentation/programming-guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/documentation/programming-guide.md
b/src/documentation/programming-guide.md
index 31db9be..b94fbee 100644
--- a/src/documentation/programming-guide.md
+++ b/src/documentation/programming-guide.md
@@ -1281,7 +1281,7 @@ Some other serializability factors you should keep in
mind are:
#### 4.3.2. Thread-compatibility {#user-code-thread-compatibility}
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 **the Beam SDKs are not
thread-safe**. 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
[email protected].
