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/06/07 03:17:00 UTC

[beam-site] branch mergebot updated (8ea8d41 -> 652fe94)

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 8ea8d41  This closes #460
 discard cc50b2e  [BEAM-2852] Update Nexmark documentation with Kafka support
     new ac0ff06  [BEAM-4479] Fixed document for Coder
     new f5956dc  [BEAM-4479] change getDefaultCoder to getCoder
     new 652fe94  This closes #459

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   (8ea8d41)
            \
             N -- N -- N   refs/heads/mergebot (652fe94)

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 3 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:
 content/documentation/programming-guide/index.html |  3 +--
 src/documentation/sdks/nexmark.md                  | 26 ++--------------------
 2 files changed, 3 insertions(+), 26 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.

[beam-site] 03/03: This closes #459

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 652fe94a65ce24d8a22881937e4f73020d8a7472
Merge: c46fc1e f5956dc
Author: Mergebot <me...@apache.org>
AuthorDate: Wed Jun 6 20:16:35 2018 -0700

    This closes #459

 content/documentation/programming-guide/index.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.

[beam-site] 02/03: [BEAM-4479] change getDefaultCoder to getCoder

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 f5956dc525a43fba403c8962e332ee418f041dc0
Author: Xin Wang <be...@163.com>
AuthorDate: Wed Jun 6 00:17:03 2018 +0800

    [BEAM-4479] change getDefaultCoder to getCoder
---
 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 4271fe6..03aada3 100644
--- a/content/documentation/programming-guide/index.html
+++ b/content/documentation/programming-guide/index.html
@@ -2429,7 +2429,7 @@ The following table shows the standard mapping:</p>
 
 <h4 id="default-coder-lookup">6.2.1. Looking up a default coder</h4>
 
-<p class="language-java">You can access the <code class="highlighter-rouge">CoderRegistry</code> for a given pipeline
+<p class="language-java">You can use the method <code class="highlighter-rouge">CoderRegistry.getCoder</code> to determine the default Coder for a Java type. You can access the <code class="highlighter-rouge">CoderRegistry</code> for a given pipeline
 by using the method <code class="highlighter-rouge">Pipeline.getCoderRegistry</code>. This allows you to determine
 (or set) the default Coder for a Java type on a per-pipeline basis: i.e. “for
 this pipeline, verify that Integer values are encoded using

-- 
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.

[beam-site] 01/03: [BEAM-4479] Fixed document for Coder

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 ac0ff06f909ad03ebdff5fcc0ed65ecaf70f7703
Author: Xin Wang <xi...@apache.org>
AuthorDate: Tue Jun 5 21:40:00 2018 +0800

    [BEAM-4479] Fixed document for Coder
---
 content/documentation/programming-guide/index.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/content/documentation/programming-guide/index.html b/content/documentation/programming-guide/index.html
index 1fc81da..4271fe6 100644
--- a/content/documentation/programming-guide/index.html
+++ b/content/documentation/programming-guide/index.html
@@ -2429,8 +2429,7 @@ The following table shows the standard mapping:</p>
 
 <h4 id="default-coder-lookup">6.2.1. Looking up a default coder</h4>
 
-<p class="language-java">You can use the method <code class="highlighter-rouge">CoderRegistry.getDefaultCoder</code> to determine the default
-Coder for a Java type. You can access the <code class="highlighter-rouge">CoderRegistry</code> for a given pipeline
+<p class="language-java">You can access the <code class="highlighter-rouge">CoderRegistry</code> for a given pipeline
 by using the method <code class="highlighter-rouge">Pipeline.getCoderRegistry</code>. This allows you to determine
 (or set) the default Coder for a Java type on a per-pipeline basis: i.e. “for
 this pipeline, verify that Integer values are encoded using

-- 
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.