You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2018/07/10 09:11:05 UTC

Slack digest for #general - 2018-07-10

2018-07-09 09:46:50 UTC - Idan: @Sijie Guo sure. link to project
----
2018-07-09 09:49:33 UTC - Ivan Kelly: @Sijie Guo i have a very simple repro for this. Let's pull this in at next triage
----
2018-07-09 12:44:25 UTC - Chris Miller: It's not clear to me from the documentation how to do pub/sub (i.e. multiple consumers all receiving all messages on a topic). The exclusive/failover/shared subscription types only cover various scenarios where a given message is only consumed by a single consumer. Do I need to create unique subscription names for each consumer? If so, is there a recommended approach (eg UUIDs)?
----
2018-07-09 13:11:10 UTC - Ivan Kelly: yes, unique subscription names
+1 : Chris Miller, Ali Ahmed
----
2018-07-09 20:36:04 UTC - Grant Wu: I have a dumb question
----
2018-07-09 20:36:18 UTC - Grant Wu: What’s the intended usage of the Consumer API vs the Reader API?
----
2018-07-09 20:38:24 UTC - Grant Wu: Oh, never mind, <https://pulsar.incubator.apache.org/docs/latest/getting-started/ConceptsAndArchitecture/> helped
----
2018-07-09 20:39:13 UTC - Ali Ahmed: I think of consumer api as higher level and reader as lower level if that helps
----
2018-07-09 20:39:33 UTC - Grant Wu: @Matteo Merli Uh, follow up to my question from last week about getting messages between a range of timestamps
----
2018-07-09 20:39:41 UTC - Grant Wu: Do you think it would be useful to have this in the Reader API?
----
2018-07-09 20:42:00 UTC - Grant Wu: In my current use case, where we want to be able to get messages between a range of timestamps, I’m looking at making a temporary subscription, using the resetCursor admin API thing to reset it, reading off messages until I get to the desired one, then closing the connection
----
2018-07-09 20:42:13 UTC - Grant Wu: I think just putting this in the Reader API might be a more natural fit
----
2018-07-09 20:42:34 UTC - Grant Wu: I can probably work on this myself if you think it’s appropriate
----
2018-07-10 00:10:04 UTC - Matteo Merli: I see, it could be possible to add to the configuration for the `ReaderBuilder` to specify a time-range. I guess the reset cursor should be done internally when establishing the reader. 

To make it more generic, what about just specifying the “start-timestamp”? It’s easy enough for the application to stop reading once message publishTime are &gt;X anyway
----
2018-07-10 00:10:28 UTC - Matteo Merli: ^^ @Grant Wu
----
2018-07-10 00:13:00 UTC - Grant Wu: Hrm
----
2018-07-10 00:13:36 UTC - Grant Wu: Yeah that ought to work I think?  Would it make sense to have the end time be an optional parameter
----
2018-07-10 00:23:16 UTC - Grant Wu: Wait sorry about dumb question
----
2018-07-10 00:23:48 UTC - Grant Wu: How does the reader interface interact with message acknowledgement
----
2018-07-10 02:08:20 UTC - Matteo Merli: @Grant Wu The reader doesn’t deal with acknowledgement. The message id has to be tracked manually (unlike with Consumer). In any case if it gets positioned based on the timestamp, you won’t need to specify anything else.
----
2018-07-10 02:09:18 UTC - Matteo Merli: <!here> Remainder for tomorrow afternoon meetup at Yahoo/Oath in Sunnyvale: <https://www.meetup.com/SF-Bay-Area-Apache-Pulsar-Meetup/events/252312389/>
+1 : jia zhai, Ali Ahmed, Sijie Guo
bananadance : jia zhai, Ali Ahmed, Sijie Guo
----
2018-07-10 02:09:34 UTC - Matteo Merli: @Matteo Merli pinned a message to this channel.
----
2018-07-10 02:39:51 UTC - Grant Wu: Sigh, someone happened to remind me - is there a CLA or anything I ought to get cleared?
----
2018-07-10 03:07:29 UTC - Matteo Merli: Nope, no CLA is needed per Apache policies 
----
2018-07-10 07:24:50 UTC - Praphan: @Praphan has joined the channel
----