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

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


The following commit(s) were added to refs/heads/master by this push:
     new 25662b4  Clarify initial subscription positioning (#4126)
25662b4 is described below

commit 25662b428e30f06385386e7f840e45fac13e7f4e
Author: Grant Wu <grant...@gmail.com>
AuthorDate: Thu Apr 25 08:14:34 2019 +0300

    Clarify initial subscription positioning (#4126)
---
 site2/docs/concepts-clients.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site2/docs/concepts-clients.md b/site2/docs/concepts-clients.md
index 4048708..ec76747 100644
--- a/site2/docs/concepts-clients.md
+++ b/site2/docs/concepts-clients.md
@@ -23,7 +23,7 @@ Whenever the TCP connection breaks, the client will 
immediately re-initiate this
 
 ## Reader interface
 
-In Pulsar, the "standard" [consumer 
interface](concepts-messaging.md#consumers) involves using consumers to listen 
on [topics](reference-terminology.md#topic), process incoming messages, and 
finally acknowledge those messages when they've been processed. Whenever a 
consumer connects to a topic, it automatically begins reading from the earliest 
un-acked message onward because the topic's cursor is automatically managed by 
Pulsar.
+In Pulsar, the "standard" [consumer 
interface](concepts-messaging.md#consumers) involves using consumers to listen 
on [topics](reference-terminology.md#topic), process incoming messages, and 
finally acknowledge those messages when they've been processed.  Whenever a new 
subscription is created, it is initially positioned at the end of the topic (by 
default), and consumers associated with that subscription will begin reading 
with the first message created afterwards.  Whenever a consumer  [...]
 
 The **reader interface** for Pulsar enables applications to manually manage 
cursors. When you use a reader to connect to a topic---rather than a 
consumer---you need to specify *which* message the reader begins reading from 
when it connects to a topic. When connecting to a topic, the reader interface 
enables you to begin with:
 

Reply via email to