You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by me...@apache.org on 2018/04/30 18:42:39 UTC
[beam-site] branch mergebot updated (454a926 -> 8f89018)
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
discard 454a926 This closes #430
discard 46ac20f [BEAM-4177] Clarify thread contraint in Programming Guide 4.3.2
new e384683 [BEAM-4177] Clarify thread contraint in Programming Guide 4.3.2
new 8f89018 This closes #430
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (454a926)
\
N -- N -- N refs/heads/mergebot (8f89018)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.
[beam-site] 01/02: [BEAM-4177] Clarify thread contraint in
Programming Guide 4.3.2
Posted by me...@apache.org.
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
commit e38468394f789dbc0bb8ef05384f5279a9eeddbb
Author: John MacMillan <jo...@ca.ibm.com>
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
mergebot-role@apache.org.
[beam-site] 02/02: This closes #430
Posted by me...@apache.org.
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
commit 8f89018024412c45e7039aeaaac8307dc16cfc83
Merge: 67836af e384683
Author: Mergebot <me...@apache.org>
AuthorDate: Mon Apr 30 11:42:03 2018 -0700
This closes #430
src/documentation/programming-guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.