2019-02-06 09:54:01 UTC - Sai Phanindhra: @Sai Phanindhra has joined the channel
----
2019-02-06 15:32:56 UTC - Karthik Palanivelu: No Change I made and it is just a
version upgrade of pulsar. I am not using helm, just using kubectl apply to
deploy the components
----
2019-02-06 15:35:33 UTC - Karthik Palanivelu: Version 2.1.1 is working fine for
me but 2.2.1 version I have this issue. Let me investigate this issue based on
above statement and will let you know.
----
2019-02-06 16:20:29 UTC - Jonathan Budd: Hi @Matteo Merli - Is there any slated
timeframe for the next release, ie a release that would include the merged
recovery mechanism that we discussed in this thread?
----
2019-02-06 16:29:13 UTC - Matteo Merli: @Jonathan Budd we plan to start cutting
the release by the end of the week, with expected release by next week
----
2019-02-06 16:29:38 UTC - Jonathan Budd: Great, thank you!
----
2019-02-06 17:00:44 UTC - Karthik Palanivelu: Thanks for your input, PULSAR_MEM
is introduced in this version on pulsar_env.sh file. I removed it and it works
fine. Is this a bug?
----
2019-02-06 17:08:45 UTC - Will McCarley: @Will McCarley has joined the channel
----
2019-02-06 19:13:38 UTC - Ambud Sharma: ```bin/pulsar-admin persistent
partitioned-stats <persistent://logging/benchmark/b2> --per-partition
Internal topics have not been generated yet
Reason: Internal topics have not been generated yet``` getting this error when
trying to check topic stats
----
2019-02-06 19:15:25 UTC - Ambud Sharma: is there a command to `list current
topic-partition to broker assignments` ?
----
2019-02-06 20:02:17 UTC - Matteo Merli: In this case, only the metadata was
created, but the actual partitions are not there yet
----
2019-02-06 20:02:32 UTC - Matteo Merli: these will be created when you start
using the topic
----
2019-02-06 20:03:53 UTC - Matteo Merli: > is there a command to `list
current topic-partition to broker assignments` ?
Yes, you can lookup a specific partition with :
```
pulsar-admin topics lookup my-topic-partition-0
```
----
2019-02-06 20:15:33 UTC - Ambud Sharma: @Matteo Merli we published about 2GB of
data but there are no stats available
----
2019-02-06 20:15:50 UTC - Ambud Sharma: I am able to read data as well for this
topic
----
2019-02-06 20:27:43 UTC - Matteo Merli: Uhm, that should be working. Can you
try getting the stats for the individual partitions?
`pulsar-admin topics stats my-topic-partition-0`
----
2019-02-06 20:36:04 UTC - Ambud Sharma: @Matteo Merli getting a response for
only 1 partition. Rest of them: ```Topic not found```
----
2019-02-06 20:38:41 UTC - Ambud Sharma: Is there a way to specify partition via
the reader API: ```client.newReader().readerName("test").topic("b1")
.startMessageId(MessageId.earliest).create();```
----
2019-02-06 21:17:06 UTC - Matteo Merli: Yes, the partitions are named like
`b1-partition-0` and so on
----
2019-02-06 21:29:58 UTC - Ambud Sharma: thanks @Matteo Merli
----
2019-02-06 22:03:17 UTC - Ambud Sharma:
```client.newReader().readerName("test").topic("b2-partition-0")
.startMessageId(MessageId.earliest).create()```
doesn't seem to be reading data however using `b2` works
----
2019-02-06 22:07:33 UTC - Ambud Sharma: we are hoping to manage consumer
offsets ourselves
----
2019-02-07 08:11:45 UTC - dba: Hi guys. Going well with the workshop! I have
two questions:
Do you have an example of a (sliding) window function in pulsar?
If we set "parallelism" to more than 1, does "retain-ordering" then ensure
ordering when inserting to the output topic? or how does it work?
----
