[flink] branch master updated: [FLINK-13125] Make PubSub stability warning more prominent

[rm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rmetzger pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/master by this push:
     new 4488523  [FLINK-13125] Make PubSub stability warning more prominent
4488523 is described below

commit 44885233d42ba919d20bcbb4760c89ffe9461d96
Author: Robert Metzger <rm...@apache.org>
AuthorDate: Fri Jul 5 16:58:05 2019 +0200

    [FLINK-13125] Make PubSub stability warning more prominent
---
 docs/dev/connectors/pubsub.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/docs/dev/connectors/pubsub.md b/docs/dev/connectors/pubsub.md
index 7c14cd5..0ee8187 100644
--- a/docs/dev/connectors/pubsub.md
+++ b/docs/dev/connectors/pubsub.md
@@ -1,6 +1,6 @@
 ---
-title: "Google PubSub"
-nav-title: PubSub
+title: "Google Cloud PubSub"
+nav-title: Google Cloud PubSub
 nav-parent_id: connectors
 nav-pos: 7
 ---
@@ -24,7 +24,7 @@ under the License.
 -->
 
 This connector provides a Source and Sink that can read from and write to
-[Google PubSub](https://cloud.google.com/pubsub). To use this connector, add the
+[Google Cloud PubSub](https://cloud.google.com/pubsub). To use this connector, add the
 following dependency to your project:
 
 {% highlight xml %}
@@ -35,13 +35,17 @@ following dependency to your project:
 </dependency>
 {% endhighlight %}
 
+<p style="border-radius: 5px; padding: 5px" class="bg-danger">
+<b>Note</b>: This connector has been added to Flink recently. It has not received widespread testing yet.
+</p>
+
 Note that the streaming connectors are currently not part of the binary
 distribution. See
 [here]({{ site.baseurl }}/dev/projectsetup/dependencies.html)
 for information about how to package the program with the libraries for
 cluster execution.
- 
-This pubsub connector has not received widespread testing yet.
+
+
 
 ## Consuming or Producing PubSubMessages
 
@@ -143,7 +147,7 @@ env.addSource(pubsubSource)
 
 There are several reasons why a message might be send multiple times, such as failure scenarios on Google PubSub's side.
 
-Another reason is when the acknowledgement deadline has past. This is the time between receiving the message and between acknowledging the message. The PubSubSource will only acknowledge a message on successful checkpoints to guarantee Atleast-Once. This does mean if the time between successful checkpoints is larger than the acknowledgment deadline of your subscription messages will most likely be processed multiple times.
+Another reason is when the acknowledgement deadline has passed. This is the time between receiving the message and between acknowledging the message. The PubSubSource will only acknowledge a message on successful checkpoints to guarantee Atleast-Once. This does mean if the time between successful checkpoints is larger than the acknowledgment deadline of your subscription messages will most likely be processed multiple times.
 
 For this reason it's recommended to have a (much) lower checkpoint interval than acknowledgement deadline.