Slack digest for #dev - 2018-09-18

[Apache Pulsar Slack]

2018-09-17 17:50:48 UTC - Rajan Dhabalia: @Sijie Guo @Matteo Merli do you know 
if is there any procedure book present which should be followed for upgrading 
bookkeeper to 4.7

2018-09-17 17:51:34 UTC - Matteo Merli: There’s no particular step involved

2018-09-17 17:51:57 UTC - Matteo Merli: (except for the authentication stuff 
from yahoo branch)

2018-09-17 17:52:04 UTC - Rajan Dhabalia: ok..thanks

Slack digest for #dev - 2018-09-14

[Apache Pulsar Slack]

2018-09-13 09:30:04 UTC - Xavier Baques: @Xavier Baques has joined the channel

Slack digest for #dev - 2018-09-12

[Apache Pulsar Slack]

2018-09-11 15:37:39 UTC - Sijie Guo: here can committers review the 2.1.1 
release please!

Slack digest for #dev - 2018-09-11

[Apache Pulsar Slack]

2018-09-10 17:55:43 UTC - Sijie Guo: @Rajan Dhabalia @Matteo Merli: can you 
review the Dead Letter Topic pr? 
 would like to include 
this as part of 2.2 release.

2018-09-10 17:57:19 UTC - Rajan Dhabalia: I missed it.. sure, I will do it..

Slack

[Dave Fisher]

Hi -

Regarding Slack. Is this a free account? Who on the PPMC has control?

Matteo - how do you run the daily script to send a digest of Slack 
conversations to dev@?

Regards,
Dave

Sent from my iPhone

Slack digest for #dev - 2018-08-30

[Apache Pulsar Slack]

2018-08-29 09:41:20 UTC - Mark Addison: @Mark Addison has joined the channel

Slack digest for #dev - 2018-08-22

[Apache Pulsar Slack]

2018-08-21 09:20:39 UTC - Bharadwaj R Embar: @Bharadwaj R Embar has joined the 
channel

Slack digest for #dev - 2018-08-17

[Apache Pulsar Slack]

2018-08-16 19:56:37 UTC - Sijie Guo: @Rajan Dhabalia can you take a look at 
this PR 

Slack digest for #dev - 2018-08-16

[Apache Pulsar Slack]

2018-08-15 19:45:48 UTC - Sebastian Schepens: @Sebastian Schepens has joined 
the channel

Slack digest for #dev - 2018-08-04

[Apache Pulsar Slack]

2018-08-03 17:34:31 UTC - Yuvaraj Loganathan: @Yuvaraj Loganathan has joined 
the channel

2018-08-03 19:38:08 UTC - Knkn: @Knkn has joined the channel

Slack digest for #dev - 2018-08-03

[Apache Pulsar Slack]

2018-08-02 19:38:01 UTC - slackbot: This message was deleted.

2018-08-02 19:41:27 UTC - Grant Wu: I think this belongs in <#C5Z4T36F7|general>

2018-08-02 19:41:43 UTC - Adam Williams: thanks, will delete  move

Slack digest for #dev - 2018-07-25

[Apache Pulsar Slack]

2018-07-24 18:21:27 UTC - Grant Wu: wait, why is this using `/lookup/v2`

2018-07-24 18:21:30 UTC - Grant Wu: that just seems inconsistent

2018-07-24 18:21:30 UTC - Grant Wu: 


2018-07-24 18:25:02 UTC - Matteo Merli: Yes, it is inconsistent, but that’s 
because of a long story. 

What became Pulsar was already the “v2” of another messaging system at Yahoo. 
That’s why the lookup handlers were already versioned.

2018-07-24 18:26:06 UTC - Grant Wu: Oh, that’s awkward.

2018-07-24 18:27:18 UTC - Grant Wu: Oh well.

2018-07-24 18:27:34 UTC - Matteo Merli: We cannot remove that endpoint, but for 
Pulsar 2.x the endpoint for lookup was changed 
 * Pulsar 1.x topics -- `lookup/v2/destination/`
  * Pulsar 2.x topics -- `lookup/v2/topic/`

2018-07-24 18:27:55 UTC - Grant Wu: Yeah I need to work on that

2018-07-24 18:29:01 UTC - Grant Wu: Unfortunately I don’t think my employer 
really understands the collaborative nature of open source, I have to work on 
everything not directly benefiting my employer on the side

2018-07-24 18:30:32 UTC - Grant Wu: Oh, I did hit that already with 


2018-07-24 18:31:31 UTC - Matteo Merli: I see, then the ` +{% endpoint GET 
/lookup/v2/destination/persistent/:tenant:namespace/:topic %} ` needs to be ` 
/lookup/v2/topic/persistent/:tenant:namespace/:topic`

2018-07-24 18:33:46 UTC - Grant Wu: oh

2018-07-24 18:33:48 UTC - Grant Wu: noted

2018-07-24 18:34:01 UTC - Grant Wu: also should there be a `/` between 
`:tenant` and `:namespace`

2018-07-24 18:34:16 UTC - Matteo Merli: oh, true

2018-07-24 18:34:39 UTC - Matteo Merli: thanks for reviewing and fixing all 
these docs !

2018-07-24 18:34:42 UTC - Grant Wu: I was planning on doing a full grep for 
`destination` later

2018-07-24 18:35:03 UTC - Grant Wu: Yeah no problem

2018-07-24 18:35:14 UTC - Grant Wu: Incidentally I have written a very 
barebones Javascript client (like, only supports exclusive subscriptions!) that 
uses the websocket transport

2018-07-24 18:35:26 UTC - Grant Wu: I may someday convince my employer to 
release that

2018-07-24 18:35:49 UTC - Grant Wu: The problem would be that features would 
get added as we need them, and we don’t really use very many features

2018-07-24 18:36:15 UTC - Matteo Merli: yes, that would yield to a lot of 
results.. I did the conversion destination - topic in a huge number of 
places several months ago — but many were left out.  I would say docs are the 
most important — and in tests we shouldn’t worry too much

2018-07-24 18:37:24 UTC - Grant Wu: can you look at that first question I asked 
yesterday that sijieg said they’d look at earlier?

2018-07-24 18:37:48 UTC - Grant Wu: 

 the URL doesn’t seem to have a command o.o

2018-07-24 18:40:00 UTC - Matteo Merli: true, let me check the code

2018-07-24 18:42:41 UTC - Matteo Merli: This is the method to create a 
subscription through the REST API: 

```
@PUT
@Path("/{tenant}/{namespace}/{topic}/subscription/{subscriptionName}")
@ApiOperation(value = "Reset subscription to message position closest to 
given position.", notes = "Creates a subscription on the topic at the specified 
message id")
@ApiResponses(value = { @ApiResponse(code = 403, message = "Don't have 
admin permission"),
@ApiResponse(code = 404, message = "Topic/Subscription does not 
exist"),
@ApiResponse(code = 405, message = "Not supported for partitioned 
topics") })
public void createSubscription(@PathParam("tenant") String tenant, 
@PathParam("namespace") String namespace,
@PathParam("topic") @Encoded String topic, 
@PathParam("subscriptionName") String subscriptionName,
@QueryParam("authoritative") @DefaultValue("false") boolean 
authoritative, MessageIdImpl messageId) {
validateTopicName(tenant, namespace, topic);
internalCreateSubscription(subscriptionName, messageId, authoritative);
}
```

2018-07-24 18:42:57 UTC - Matteo Merli: the doc there is wrong/misleading.

2018-07-24 18:43:37 UTC - Matteo Merli: there is no action since this is a PUT 
operation on “subscription” resource. It takes a message Id and initialize the 
subscription on that message Id

2018-07-24 18:44:13 UTC - Matteo Merli: ` @ApiOperation(value = "Reset 
subscription to message position closest to given position.", notes = "Creates 
a subscription on the topic at the specified message id")`
should be changed into 

`@ApiOperation(value = "Creates a subscription on the 

Slack digest for #dev - 2018-07-24

[Apache Pulsar Slack]

2018-07-23 17:34:20 UTC - Grant Wu: I don’t see a command in this URL 


2018-07-23 17:43:57 UTC - Grant Wu: Is that correct?

2018-07-23 20:22:42 UTC - Grant Wu: Namely, it is unclear what the “given 
position” is

2018-07-23 20:23:32 UTC - Grant Wu: 

 also, for this, what format is the timestamp expected in?

2018-07-23 20:23:35 UTC - Grant Wu: A Unix timestamp?

2018-07-23 20:23:43 UTC - Grant Wu: @Sijie Guo

2018-07-23 20:24:06 UTC - Sijie Guo: @Grant Wu one second

2018-07-23 20:24:47 UTC - Grant Wu: :thumbsup:

2018-07-23 20:25:01 UTC - Sijie Guo:  what format is the timestamp expected 
in?

yes it is a unix timestamp.

2018-07-23 20:25:18 UTC - Sijie Guo: I will come back to your first question 
later

2018-07-23 20:28:08 UTC - Grant Wu: Okay, cool.  We probably ought to document 
that; it’s a bit confusing because it seems like the CLI has a bit of sugar 
that lets you specific relative timestamps, which isn’t in the REST API

Slack digest for #dev - 2018-07-21

[Apache Pulsar Slack]

2018-07-20 14:30:24 UTC - Grant Wu: @Sijie Guo 

 Should this be changed?

2018-07-20 16:22:54 UTC - Sijie Guo: Good question. That seems to be a result 
of admin command. It probably don’t need to be changed.

2018-07-20 16:30:38 UTC - Matteo Merli: yes, that is the field name for topic 
level authentication in the namespace configuration. We cannot change it 
(easily) because it would not match with the policies that one might have 
already configured.

Slack digest for #dev - 2018-07-20

[Apache Pulsar Slack]

2018-07-19 15:13:32 UTC - Grant Wu: @Sijie Guo do we want to get rid of all 
references to “destination”?

2018-07-19 15:13:38 UTC - Grant Wu: Or just `:destination`

2018-07-19 15:13:49 UTC - Grant Wu: for an example of what I mean, see 


2018-07-19 16:25:41 UTC - Sijie Guo: It would be better to remove all

2018-07-19 20:02:47 UTC - Grant Wu: ugh

2018-07-19 20:03:03 UTC - Grant Wu: ```
grant.wu@MBP00245s-MacBook-Pro:~/apache-pulsar-2.0.1-incubating ⇒ 
bin/pulsar-admin topics subscriptions
Main parameters are required ("
")

Usage: pulsar-admin topics [options] [command] [command options]
  Commands:
list  Get the list of topics under a namespace.
  Usage: list [options] property/namespace
```

2018-07-19 20:03:10 UTC - Grant Wu: There’s “property” everywhere here too as 
well

2018-07-19 20:04:38 UTC - Matteo Merli: @Grant Wu I think most of these were 
already fixed in master

2018-07-19 20:04:44 UTC - Grant Wu: ah

2018-07-19 20:04:58 UTC - Matteo Merli: `git grep "property/namespace/topic"` 
doesn’t return anything

2018-07-20 00:07:02 UTC - Sijie Guo: the new RC for 2.1.0 release is out, 
please help check and vote it - 

+1 : Rajan Dhabalia, Ali Ahmed, Matteo Merli, jia zhai

2018-07-20 00:07:17 UTC - Sijie Guo: @Sijie Guo pinned a message to this 
channel.

Slack digest for #dev - 2018-07-19

[Apache Pulsar Slack]

2018-07-18 16:02:34 UTC - Grant Wu: @Grant Wu has joined the channel

2018-07-18 17:16:55 UTC - chris: @chris has joined the channel

Slack digest for #dev - 2018-07-18

[Apache Pulsar Slack]

2018-07-17 23:52:15 UTC - Jason Buster: @Jason Buster has joined the channel

Slack digest for #dev - 2018-07-10

[Apache Pulsar Slack]

2018-07-09 21:17:59 UTC - Rajan Dhabalia:  correct, currently the 
implementation expects an external source to trigger get metrics and reset 
periodically like the rest of the metrics from the broker. Prometheus will do 
this automatically for you but if you want to get it yourself, you will have to 
schedule a task to do that.

@Jerry Peng I will create a PR to make this change so, we can use different 
metrics-collection

2018-07-09 21:34:52 UTC - Jerry Peng: ok

2018-07-09 23:07:41 UTC - Matteo Merli: @Rajan Dhabalia I was looking into 
 

According to protobuf docs, the encoding should be the same for a “repeated” 
field that only appears once. 
 

Which versions consumer/broker are you trying and what would be a way to 
reproduce easily?

2018-07-10 07:53:06 UTC - Rajan Dhabalia:  The code should already be 
sending 1 single ack if the broker is  2.0 :

I see, I missed it to check.

I think the issue is that I have cherry-picked 
ActiveConsumerListener-change:
 into broker-1.22 to support function on broker-1.22 and this PR upgraded 
pulsar-broker version=V12 and because of that client was sending group-ack to 
broker which broker couldn't understand.
Thanks for pointing it out, I will fix our internal broker.

Slack digest for #dev - 2018-07-06

[Apache Pulsar Slack]

2018-07-05 20:35:28 UTC - Rajan Dhabalia: hi @Sijie Guo @Jerry Peng @Sanjeev 
Kulkarni @Matteo Merli 

I have a qq to understand how stats/metrics works in functions.
1. I can see that JavaInstanceRunnable has a method to generate and reset 
metrics:


2. It is being triggered by FunctionsStatsGenerator


Questions:
1. Who triggers stats-generation at FunctionsStatsGenerator which can generate 
and reset stats every 1 minute to capture rate-per-second for every 
function-stats? 
as a user, if I don't want to use prometheous then do I have to schedule a task 
which can generate-and-reset the stats every x (1) minute?

2. Right now, user-metrics is being collected for function-processing: 

as a user, if I also want to capture user-metrics at Sink then is if fine if I 
can pass same context to sink to capture user-metrics?

2018-07-05 21:34:17 UTC - Jerry Peng: @Rajan Dhabalia responding inline
1. Who triggers stats-generation at FunctionsStatsGenerator which can generate 
and reset stats every 1 minute to capture rate-per-second for every 
function-stats? 
as a user, if I don’t want to use prometheous then do I have to schedule a task 
which can generate-and-reset the stats every x (1) minute?

correct, currently the implementation expects an external source to trigger get 
metrics and reset periodically like the rest of the metrics from the broker. 
Prometheus will do this automatically for you but if you want to get it 
yourself, you will have to schedule a task to do that.

2018-07-05 21:38:00 UTC - Jerry Peng: 2. Right now, user-metrics is being 
collected for function-processing: 

as a user, if I also want to capture user-metrics at Sink then is if fine if I 
can pass same context to sink to capture user-metrics? 

How do you intend to pass the context to the sink?  We cannot easily add the 
same context to the sink interface since the context passed into a function 
assumes its getting data from a topic and writing it to another topic. Which 
might not be the case for a sink.  We can potentially expose a modified 
interface to record metrics

2018-07-05 21:43:16 UTC - Rajan Dhabalia:  How do you intend to pass the 
context to the sink?

I mean, function is capturing user-metrics from the context:


if we can pass same context to sink eg: KinesisSink then KinesisSink can add 
its user-metrics in it such as eg: kinesisPublishLatency, kinesisSuccess, 
kinesisFailures ..
so, function doesn't have to maintain multiple contexts and all user-metrics 
can be captured by one context..

2018-07-05 21:49:40 UTC - Rajan Dhabalia:  We cannot easily add the same 
context to the sink interface since the context passed into a function assumes 
its getting data from a topic and writing it to another topic. Which might not 
be the case for a sink.  

That's true, we can't pass same context to sink.. 

 We can potentially expose a modified interface to record metrics

correct..we mainly require to pass `ContextImpl.accumulatedMetrics` to sink 
which can be used to capture metrics

2018-07-05 21:52:04 UTC - Rajan Dhabalia: so, would you like to create a PR or 
I can create a PR to accommodate this change.?

2018-07-05 21:53:43 UTC - Jerry Peng: actually we can probably use the same 
context in sink as well since with a sink, the source is always PulsarSource 
and the function is set to the identity function

2018-07-05 21:55:37 UTC - Jerry Peng: but for the sake of keeping things 
separate/modular, lets have different interfaces

2018-07-05 21:55:57 UTC - Jerry Peng: The “Context” interface will be for 
functions and we can create a “SinkContext” for the sink

2018-07-05 21:56:10 UTC - Jerry Peng: ContextImpl can implement both

2018-07-05 21:56:45 UTC - Jerry Peng: maybe the SinkContext can just expose a 
subset of the functionality in ContextImpl

2018-07-05 21:57:37 UTC - Jerry Peng: @Rajan Dhabalia how does that sound?

2018-07-05 22:05:27 UTC - Rajan Dhabalia: yes, it seems we can can't break 
existing sink-api: `void write(RecordContext inputRecordContext, T value)`
So,  SinkContext = `RecordContext` can implement `Context` and it can implement 
two more apis from context
1. `void 

Slack digest for #dev - 2018-06-21

[Apache Pulsar Slack]

2018-06-20 17:50:08 UTC - Rajan Dhabalia: sure

2018-06-21 03:58:07 UTC - Kanaderu Fukuda: @Kanaderu Fukuda has joined the 
channel

Slack digest for #dev - 2018-06-20

[Apache Pulsar Slack]

2018-06-20 05:15:16 UTC - Rene Hernandez: @Rene Hernandez has joined the channel

2018-06-20 07:07:06 UTC - Sijie Guo: @Rajan Dhabalia @Jai Asher can you guys 
review this change -  ?

2018-06-20 07:07:38 UTC - Sijie Guo: since I am not very familiar with 
non-persistent topic, it would be good you guys can review to make sure this 
change won’t affect your use cases.

Slack digest for #dev - 2018-06-12

[Apache Pulsar Slack]

2018-06-11 20:43:13 UTC - Jai Asher: @Matteo Merli @Sijie Guo @Rajan Dhabalia 
For 1.22.1 candidate 2 do we need to make changes and release candidate 3 OR 
just make the corrections in 2.0
```
Thanks Yang, Justin and Craig for the discussion.

We will correct these files by removing ASF header, leaving only BSD header
+ comment.

Matteo
```

2018-06-11 20:46:44 UTC - Jai Asher: 


2018-06-11 20:47:07 UTC - Sijie Guo: I guess we need to address them. 
otherwise, there will be pushed back from incubator list. but @Matteo Merli 
might have a different view.

2018-06-11 20:47:42 UTC - Jai Asher: ok I will wait till EOD before creating 
candidate 3.

2018-06-11 21:24:19 UTC - Matteo Merli: I don't think there was any -1 there

2018-06-11 21:52:45 UTC - Matteo Merli: @Jai Asher there are already 3 binding 
+1s and no -1s. We’ll address issue in 2.1

Slack digest for #dev - 2018-06-09

[Apache Pulsar Slack]

2018-06-08 19:17:16 UTC - Sanjeev Kulkarni: @Rajan Dhabalia I’m seeing 
PulsarSinkE2ETest time out the whole build repeatedly. example 
. Any 
insight?

2018-06-08 19:46:27 UTC - Rajan Dhabalia: let me check

2018-06-08 19:59:38 UTC - Rajan Dhabalia: it seems test is getting stuck while 
shutting down the pulsar-service after test completes..
```
 java.util.concurrent.CountDownLatch.await() @bci=5, line=231 (Interpreted 
frame)
org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.shutdown()
```
i will add the timeout to test and will investigate to fix it soon..
+1 : jia zhai

Slack digest for #dev - 2018-06-08

[Apache Pulsar Slack]

2018-06-07 13:52:50 UTC - Chris Miller: @Chris Miller has joined the channel

Slack digest for #dev - 2018-06-07

[Apache Pulsar Slack]

2018-06-06 17:17:26 UTC - Sanjeev Kulkarni: @Sanjeev Kulkarni has joined the 
channel

2018-06-06 17:17:52 UTC - Sanjeev Kulkarni: getting this stacktrace while 
trying to submitting functions

2018-06-06 17:17:54 UTC - Sanjeev Kulkarni: 09:34:06.995 
[FunctionActionerThread] INFO  
org.apache.pulsar.functions.worker.FunctionActioner - Function package file 
/tmp/
pulsar_functions/public/default/kafkasource/0/utils.jar.0.4f714650-2132-4c9c-afc3-ec3c8e0bfe12
 will be downloaded from packag
ePath: 
“public/default/kafkasource/da9a0037-99af-4989-87ff-c4d5fb17d188-core-0.0.1.jar”

09:34:09.204 [FunctionActionerThread] INFO  
org.apache.pulsar.functions.worker.FunctionActioner - Function package file is 
li
nked from 
/tmp/pulsar_functions/public/default/kafkasource/0/utils.jar.0.4f714650-2132-4c9c-afc3-ec3c8e0bfe12
 to /tmp/pulsar_
functions/public/default/kafkasource/0/utils.jar
09:34:09.211 [FunctionActionerThread] INFO  
org.apache.pulsar.functions.worker.FunctionActioner - Error starting function
java.lang.NullPointerException: null
at 
org.apache.pulsar.functions.worker.FunctionActioner.startFunction(FunctionActioner.java:131)
 ~[org.apache.pulsar-p
ulsar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at 
org.apache.pulsar.functions.worker.FunctionActioner.lambda$new$0(FunctionActioner.java:78)
 ~[org.apache.pulsar-pul
sar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
09:34:10.148 [qtp565168593-35] ERROR 
org.apache.pulsar.functions.worker.rest.api.FunctionsImpl - Got Exception 
Getting Status
java.lang.NullPointerException: null
at 
org.apache.pulsar.functions.proto.InstanceCommunication$FunctionStatus$Builder.setFailureException(InstanceCommunication.java:1994)
 
~[org.apache.pulsar-pulsar-functions-proto-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at 
org.apache.pulsar.functions.worker.FunctionRuntimeManager.getFunctionInstanceStatus(FunctionRuntimeManager.java:255)
 
~[org.apache.pulsar-pulsar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at 
org.apache.pulsar.functions.worker.FunctionRuntimeManager.getAllFunctionStatus(FunctionRuntimeManager.java:318)
 
~[org.apache.pulsar-pulsar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at 
org.apache.pulsar.functions.worker.rest.api.FunctionsImpl.getFunctionStatus(FunctionsImpl.java:387)
 
[org.apache.pulsar-pulsar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at 
org.apache.pulsar.functions.worker.rest.api.v2.FunctionApiV2Resource.getFunctionStatus(FunctionApiV2Resource.java:109)
 
[org.apache.pulsar-pulsar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:1.8.0_151]

2018-06-06 17:17:58 UTC - Sanjeev Kulkarni: this is happening in master

2018-06-06 17:18:18 UTC - Matteo Merli: @Rajan Dhabalia ^^

2018-06-06 17:18:32 UTC - Sanjeev Kulkarni: probably related with 


2018-06-06 17:49:56 UTC - Jerry Peng: @Jerry Peng has joined the channel

2018-06-06 17:57:10 UTC - Sijie Guo: @Rajan Dhabalia are you looking into it? 
or shall we be looking into it? just try to avoid duplicated work in the 
community

2018-06-06 17:58:36 UTC - Rajan Dhabalia: oh..let me check on it

2018-06-06 18:06:15 UTC - Jerry Peng: cool thanks

2018-06-06 18:31:52 UTC - Rajan Dhabalia: i found the issue.. after doing -ve 
testing for #1092, i missed to revert the change.. 

right now, I don't see any unit-test case in `worker` module which touches any 
method of `FunctionActioner`.. so, working on adding unit-test for it..

2018-06-06 19:20:12 UTC - Rajan Dhabalia: added the unit-tests
+1 : Matteo Merli, Sijie Guo, Jerry Peng

2018-06-06 21:49:42 UTC - Sanjeev Kulkarni: @Rajan Dhabalia things are still 
broken

2018-06-06 21:50:34 UTC - Sanjeev Kulkarni: 14:48:58.555 
[FunctionActionerThread] INFO  
org.apache.pulsar.functions.worker.FunctionActioner - Function package file is 
li
nked from 
/tmp/pulsar_functions/public/default/kafkasource/0/utils.jar.0.8d1a446d-f8fa-4e85-a2a2-7247af6ddd2f
 to /tmp/pulsar_
functions/public/default/kafkasource/0/utils.jar
14:48:58.565 [FunctionActionerThread] INFO  
org.apache.pulsar.functions.worker.FunctionActioner - Error starting function
java.lang.NullPointerException: null
at 
org.apache.pulsar.functions.worker.FunctionActioner.startFunction(FunctionActioner.java:132)
 ~[org.apache.pulsar-p
ulsar-functions-worker-2.1.0-incubating-SNAPSHOT.jar:2.1.0-incubating-SNAPSHOT]
at 
org.apache.pulsar.functions.worker.FunctionActioner.lambda$new$0(FunctionActioner.java:78)
 ~[org.apache.pulsar-pul

Slack digest for #dev - 2018-06-06

[Apache Pulsar Slack]

2018-06-05 22:29:26 UTC - Sijie Guo: @Rajan Dhabalia @Jai Asher any of you know 
where can I find the tag for 4.3.1.91-yahoo ?

2018-06-05 22:35:15 UTC - Rajan Dhabalia: unfortunately yahoo-bk repo doesn't 
create a tag for a release.. and it's little bit tricky to find appropriate 
commit for a given version..
But you can find artifact at: 


and commit for which, we have tag: 4.3.1.91-yahoo:


2018-06-05 22:36:18 UTC - Sijie Guo: cool thank you

2018-06-05 22:39:26 UTC - Sijie Guo: but this is based on master?

2018-06-05 22:39:55 UTC - Sijie Guo: I thought it is based on yahoo-branch?

2018-06-05 22:41:05 UTC - Matteo Merli: I’d assume it was 


2018-06-05 22:41:47 UTC - Sijie Guo: I am trying to find if 
`auditorLedgerVerificationPercentage` change is included in 4.3.1.91-yahoo

2018-06-05 22:42:58 UTC - Sijie Guo: 4.3.1.91-yahoo was 4 months ago, so I 
assume does include this auditorLedgerVerificationPercentage change

2018-06-05 22:43:18 UTC - Sijie Guo: @Rajan Dhabalia wondering if you guys set 
auditorLedgerVerificationPercentage on your production environments or not?

2018-06-05 22:43:41 UTC - Matteo Merli: it’s indeed included: 


2018-06-05 22:44:44 UTC - Sijie Guo: yeah. that’s HEAD. I would like to confirm 
that. If that’s the case, setting a default value 100% is kind of bad.

2018-06-05 22:57:13 UTC - Rajan Dhabalia: @Sijie Guo yes, my bad.. it's based 
on yahoo-4.3 as Matteo corrected..

Slack digest for #dev - 2018-06-04

[Apache Pulsar Slack]

2018-06-04 08:36:28 UTC - Alex Ott: @Alex Ott has joined the channel

Slack digest for #dev - 2018-05-26

[Apache Pulsar Slack]

2018-05-26 05:48:37 UTC - Krishna: @Krishna has joined the channel

Slack digest for #dev - 2018-05-04

[Apache Pulsar Slack]

2018-05-03 11:08:13 UTC - haphut: @haphut has joined the channel

Slack digest for #dev - 2018-05-03

[Apache Pulsar Slack]

2018-05-02 18:18:33 UTC - Sijie Guo: the first RC of 2.0 is out, please help 
check and vote it - 


2018-05-02 20:35:05 UTC - Jai Asher: Starting patch release for 1.22.1 please 
check  commits 
and let me know if you want to add anymore fixes

2018-05-02 21:19:27 UTC - Matteo Merli: @Jai Asher Take a look at 


2018-05-02 21:19:55 UTC - Matteo Merli: these were comments from 1.22 release 
voting on general@ mailing list

2018-05-02 21:20:28 UTC - Matteo Merli: I have addressed them in 2.0 release. 
Some of these might be easy to backport as well

Slack digest for #dev - 2018-04-30

[Apache Pulsar Slack]

2018-04-30 07:42:33 UTC - Song Kun: @Song Kun has joined the channel

Slack digest for #dev - 2018-04-24

[Apache Pulsar Slack]

2018-04-23 17:18:26 UTC - Sijie Guo: @Jai Asher how are we going to do 1.22.1? 
cherry-pick and push a PR and update #1631?

2018-04-23 17:32:06 UTC - Matteo Merli: I’d say we don’t need to code review 
again since the changes were already reviewed. 

We could get started by going through the list of bugs fixed in current master 

 and see what applies. 

Again, I think the easiest way would be to just stack the issues/prs in a 
github project. 

@Jai Asher, regarding the branch, 1.22.1 would be the tag, but the convention 
we have adopted always was to use `branch-1.22` as the branch name, and then 
`v1.22.1-incubating` as the tag

2018-04-23 17:55:12 UTC - Jai Asher: ok I will delete `1.22.1` branch

2018-04-23 17:58:32 UTC - Jai Asher: Also have created a project as per @Matteo 
Merli suggestion

2018-04-23 17:58:33 UTC - Jai Asher: 


2018-04-23 17:59:30 UTC - Matteo Merli: thanks, added columns

2018-04-23 23:58:39 UTC - Matteo Merli: @Jai Asher I have added few commits as 
proposed to backport. Can you go through the list as well? Also, please send a 
message to dev@ list to have more people to add fixes to be backport to 1.22.1
+1 : Jai Asher

2018-04-24 00:43:16 UTC - Sijie Guo: @Rajan Dhabalia - here is the PR : 


2018-04-24 01:26:43 UTC - Rajan Dhabalia: :+1:

2018-04-24 01:31:55 UTC - Rajan Dhabalia: @Matteo Merli @Sijie Guo I think we 
can avoid control-topic approach in replicator framework and we can try to make 
it more generic if pulsar-function provides a way to control function state(eg: 
start/stop).. you can add your feedback and views on 
 and we can quickly 
address it

Slack digest for #dev - 2018-04-23

[Apache Pulsar Slack]

2018-04-22 12:52:50 UTC - Matteo Merli: There was already branch-1.22 for this

Slack digest for #dev - 2018-04-22

[Apache Pulsar Slack]

2018-04-21 18:58:14 UTC - Mathieu Ravaux: @Mathieu Ravaux has joined the channel

2018-04-22 07:38:27 UTC - Jai Asher: @Sijie Guo @Matteo Merli 
For Patch release 1.22.1
- I have created a new branch 
- Lets use this issue to track the fixes for 1.22.1 


2018-04-22 07:39:51 UTC - Jai Asher: If all are in agreement with this approach 
then I will start the release on Monday

2018-04-22 07:47:49 UTC - Sijie Guo: Works for me 

Slack digest for #dev - 2018-04-20

[Apache Pulsar Slack]

2018-04-19 21:05:15 UTC - Doodle: @Doodle has joined the channel

2018-04-20 01:25:47 UTC - Eder Ruiz: @Eder Ruiz has joined the channel

Slack digest for #dev - 2018-04-10

[Apache Pulsar Slack]

2018-04-09 18:30:31 UTC - Dave Mannion: @Dave Mannion has joined the channel

Slack digest for #dev - 2018-04-07

[Apache Pulsar Slack]

2018-04-06 12:02:15 UTC - Igor Zubchenok: I use 1.22 release. So seems it is 
already fixed in the current source.

2018-04-06 16:40:03 UTC - Hays Prevost: @Hays Prevost has joined the channel

Slack digest for #dev - 2018-04-06

[Apache Pulsar Slack]

2018-04-05 17:44:31 UTC - Matteo Merli:  Please take a look at Tiered 
storage proposal  

 and comment on the dev@ mailing list 


2018-04-05 19:39:58 UTC - Dave Rusek: I'll leave comments this evening.

2018-04-05 20:54:11 UTC - Igor Zubchenok: Property name cannot contain 
underscore '_' ?
In debug I found that NamedEntity.checkURI method returns false

2018-04-05 20:55:30 UTC - Matteo Merli: that’s an artifact of the mapping with 
a URL.. that part would correspond to a hostname, which cannot contain `_`

2018-04-05 20:56:42 UTC - Igor Zubchenok: I see the reason of failure, but is 
it actually designed this way?

2018-04-05 20:57:16 UTC - Igor Zubchenok: I can create property with `_`, but 
cannot work it it later

2018-04-05 20:57:43 UTC - Matteo Merli: It probably could be relaxed. I think 
it was just due to parsing with Java URI class

2018-04-05 20:58:00 UTC - Matteo Merli: uhm, that shouldn’t have been allowed 
to be created then ..

2018-04-05 20:59:18 UTC - Igor Zubchenok: isn't it better don't associate 
hostname to property while checking for correctness? just use a some 
`localhost` as a host name?

2018-04-05 21:00:25 UTC - Igor Zubchenok: this check is performed on namespace 
name validation, but not on property creation.

2018-04-05 21:03:26 UTC - Matteo Merli: correct, and the thing is that the 
parsing is not using the URI anymore since a long while

2018-04-05 21:03:36 UTC - Matteo Merli: check out `TopicName` class

2018-04-05 21:04:35 UTC - Matteo Merli: so, the `_` should be now allowed, and 
in any case the property name should be validated with same method on creation

2018-04-05 21:10:58 UTC - Igor Zubchenok: Should I file it in github or it's 
already fixed in current source and will be released soon?

2018-04-05 21:11:46 UTC - Matteo Merli: Nope, not fixed yet. I was about to 
create the issue but please go ahead.

2018-04-05 21:12:04 UTC - Igor Zubchenok: :slightly_smiling_face: ok, will do

2018-04-05 21:12:13 UTC - Matteo Merli: I’ll try to fix this and the other 
issues soon

2018-04-05 21:15:41 UTC - Igor Zubchenok: 


2018-04-05 21:16:23 UTC - Matteo Merli: Thanks :+1:

2018-04-05 21:16:50 UTC - Igor Zubchenok: Did you consider implementing a 
namespace producer?

2018-04-05 21:34:36 UTC - Matteo Merli: for now we’re mostly busy in getting 
2.0 release out of the door

2018-04-05 21:34:55 UTC - Matteo Merli: lots of task to wrap up for that

2018-04-05 21:54:29 UTC - Matteo Merli: @Igor Zubchenok, actually the `_` 
should be already permitted, I just did a unit test and it was working: 

```
PropertyAdmin propertyAdmin = new PropertyAdmin(Sets.newHashSet("role1", 
"role2"), Sets.newHashSet("use"));
admin.properties().createProperty("prop_xyz", propertyAdmin);

admin.namespaces().createNamespace("prop_xyz/use/my-namespace");

String topic = "";

Producerbyte[] producer = pulsarClient.newProducer().topic(topic)
.create();

PersistentTopicStats stats = admin.persistentTopics().getStats(topic);
assertEquals(stats.publishers.size(), 1);
producer.close();
```

2018-04-05 21:55:12 UTC - Matteo Merli: the reason the pattern works is that 
`\w` already includes `_` as a matching character

2018-04-05 21:55:47 UTC - Matteo Merli: and when creating a property, I’ve 
check that the same format is performed

Slack digest for #dev - 2018-04-04

[Apache Pulsar Slack]

2018-04-03 17:11:06 UTC - Venkat: Hi Guys , I read few docs on working of 
Pulsar and looking forward to understand it better...Please let me know if 
their are any beginner issues that could be picked up...

2018-04-03 17:46:45 UTC - Matteo Merli: Hi @Venkat, we do have few issues that 
can be easy to start with. Depending on what you’re most interested into, you 
might take a look at Python3 examples: 
 or make standalone 
service work in Java9: 

2018-04-03 17:50:03 UTC - Venkat: Thanks @Matteo Merli .. Will look into it

2018-04-03 17:50:22 UTC - Matteo Merli: :+1:

2018-04-03 21:16:04 UTC - Jai Asher: I am unable to build pulsar master on my 
laptop
```
jai1@C02T21KCG8WL-lm:~/tempProjects/pulsar$ git checkout master
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
jai1@C02T21KCG8WL-lm:~/tempProjects/pulsar$ git reset --hard origin/master
HEAD is now at 19dd2c502 Delayed acks impl (#1462)
.
.
.
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project managed-ledger: Compilation failure
[ERROR] 
/Users/jai1/tempProjects/pulsar/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedLedgerFactoryImpl.java:[66,34]
 cannot find symbol
[ERROR] symbol:   class OrderedSafeExecutor
[ERROR] location: package org.apache.bookkeeper.util
[ERROR] - [Help 1]
```

Any idea why? Do I need to build the bookkeeper jar locally before building 
pulsar?

2018-04-03 21:16:22 UTC - Sijie Guo: there is one PR outstanding fixing it

2018-04-03 21:16:37 UTC - Jai Asher: Thanks :slightly_smiling_face:

2018-04-03 21:16:39 UTC - Sijie Guo: 


2018-04-03 21:16:48 UTC - Sijie Guo: here is the PR

2018-04-03 21:18:18 UTC - Matteo Merli: I made one change into BK and have the 
corresponding change for Pulsar: 


2018-04-03 21:29:53 UTC - Rajan Dhabalia: if we really want SNAPSHOT version 
temporary then can we at least use timestamp of that SNAPSHOT version which can 
prevent build failure as far as timestamp version is available at maven-repo..

2018-04-03 21:33:11 UTC - Sijie Guo: @Rajan Dhabalia good idea

2018-04-03 21:46:12 UTC - Matteo Merli: @Rajan Dhabalia Since the CI has 
already passed, can we just merge #1489. We’ll fix the snapshot version later

2018-04-03 21:46:12 UTC - Rajan Dhabalia: not sure, how many SNAPSHOT versions 
maven keeps?

2018-04-03 21:46:45 UTC - Matteo Merli: some but not forever, in any case we 
should be close to 4.7 release

2018-04-03 21:47:19 UTC - Matteo Merli: We have been testing a lot to make sure 
all the stuff merged from yahoo branch are in good shape

2018-04-03 21:48:20 UTC - Rajan Dhabalia: dismissed it

2018-04-03 21:48:29 UTC - Rajan Dhabalia: we can merge it now

2018-04-03 21:48:36 UTC - Matteo Merli: :+1:

2018-04-03 21:49:19 UTC - Matteo Merli: Ok, merged, sorry for the disruption. 
Master is now open for business again :slightly_smiling_face:

2018-04-03 23:06:23 UTC - Jai Asher: Thanks :slightly_smiling_face:

Slack digest for #dev - 2018-04-03

[Apache Pulsar Slack]

2018-04-02 17:27:14 UTC - Sahaya Andrews Albert: Got this working for aws. Had 
to make minor changes. I'll submit those changes against a separate folder for 
aws.

2018-04-02 17:40:48 UTC - Sijie Guo: @Rajan Dhabalia 

- 4.7.0-snapshot is latest master in bookkeeper. there is a nightly job running 
publishing the snapshots
- regarding the auth provider, I think there are changes to decouple it from 
protobuf. so you might need to adjust the auth provider.
- “Pulsar-Function-PIP had large number of commits which is making hard to find 
previous history commit” - those commits should be limited to 
`pulsar-function` directory only, no?

Slack digest for #dev - 2018-03-31

[Apache Pulsar Slack]

2018-03-30 16:27:53 UTC - Joe Francis: I am for  a topic level throttle.   
Connection level throttling doesn't seem to have any real world semantics - 
what does it mean to a user ?

2018-03-30 16:50:17 UTC - Matteo Merli:  Once the rateLimit is hit the 
Broker sends this command to all producers connected to the topic and expects 
clients to reject all newly published messages for stopPublishingInMs 

..so that will break ordering

 required uint64 stopPublishingInMs = 3;  

What the broker could give is an “hint” on what the rate can be for this 
particular producer. Eg: if 10 producers are connected and limit is 1K, broker 
could advertise 100/s each.

 I am for  a topic level throttle.   Connection level throttling doesn’t 
seem to have any real world semantics - what does it mean to a user ?

One thing is the goal to achieve and how to configure it. Another is how to 
reach that goal. Slowing down a connection (when the limit per-topic is 
reached) is probably the most effective way to deal with the problem

2018-03-30 19:23:21 UTC - Jai Asher:  ..so that will break ordering 
No cause we will also fail all pending acks when we fail a message - fail 
entire pending message queue, just like a reconnect scenario

So from what I understand we are in general consensus about using the "Broker 
side connection level throttling - server side limit", which is similar to the 
currnet implementation.

As for "Client Side backoff - soft throttling" building on what Rajan and 
Matteo suggested
- We have parameter `publishThrottlingRatePerTopicInMsg` like discussed 
before.
- The Broker decides what rates a producer can produce at and sends the 
new rates every X seconds (Configurable). 
- Create a new command 
```
CommandNewRates {
required uint64 producer_id = 1;
required string producer_name = 2;
// time when next permit will be available + a small random 
offset.
required double publishRate = 3;  
}
```
- Enhance `CommandProducerSuccess` to add 
`optional double publishRate = 3;`
- The Client ratelimits the Publishes based on those rate.


For Example:-
Let publishThrottlingRatePerTopicInMsg=1000 MPS
Let publishRateRefreshTime=5 seconds - broker will send CommandNewRates every 
five seconds

Time - 0 seconds 
When producer-1 connects we send the rate as 1000 MPS in CommandProducerSuccess
When producer-2 connects we send the rate as 1000 MPS in CommandProducerSuccess
When producer-3 connects we send the rate as 1000 MPS in CommandProducerSuccess
When producer-4 connects we send the rate as 1000 MPS in CommandProducerSuccess

Basically we trust all producers to behave just as we do currently.

Time - 5 seconds
producer-1 produced at 1000 MPS
producer-2 produced at 0 MPS 
producer-3 producer at 5000 MPS
producer-4 producer at 1 MPS

Broker calculates new rates  - 

Average rate = publishThrottlingRatePerTopicInMsg / total #producers  = 1000/4 
= 2500 MPS

Unused publish rate = Average rate - producer publish rate 
From producer-1 = max(0, 2500 - 1000) = 1500
From producer-2 = max(0, 2500 - 0) = 2500
From producer-3 = max(0, 2500 - 5000) = 0
From producer-4 = max(0, 2500 - 1) = 0
Total Unused publish rate = 4000 MPS

Over used publish rate = producer publish rate  - Average rate
From producer-1 = max(0,  1000 - 2500) = 0
From producer-2 = max(0, 0 - 2500) = 0
From producer-3 = max(0, 5000 - 2500) = 2500
From producer-4 = max(0, 1 - 2500) = 7500
Total Over used publish rate = 1 MPS

Ratio of over used publish rate = Over used publish rate / Total Over used 
publish rate
From producer-1 = 0 / 1 = 0
From producer-2 = 0 / 1 = 0
From producer-3 = 2500 / 1 = 0.25
From producer-4 = 7500 / 1 = 0.75


New Publish rate = Average rate + (Ratio of over used publish rate * Total 
Unused publish rate)
For producer-1 = 2500 + 0 * 4000 = 2500 MPS
For producer-2 = 2500 + 0 * 4000 = 2500 MPS
For producer-3 = 2500 + 0.25 * 4000 = 3500 MPS
For producer-4 = 2500 + 0.75 * 4000 = 5500 MPS

Broker sends new publish rates to producers and expects the clients to adhere 
to it 

If the clients don't obey the broker throttles the connection `setAutoRead off` 
till next permit is available, as discussed above in `Broker side connection 
level throttling`
This makes sures that only the connections of misbehaving producers are 
throttled.

==
Basically if a producer behaves i.e is within average publish rate (2500) - we 
trust it to continue behaving and distribute its unused rate to other producers.
==
Do you think this approach is valid enough to start off with a PIP?

2018-03-31 00:04:48 UTC - Rajan Dhabalia: - Pulsar master is pointing to: 
`bookkeeper.version4.7.0-SNAPSHOT/bookkeeper.version`
is it using same Apache Bookkeeper version?

Slack digest for #dev - 2018-03-30

[Apache Pulsar Slack]

2018-03-29 17:05:30 UTC - Sahaya Andrews Albert: What is our approach to get 
stateful bookie where the hostname/IP can be retained and if bookie is using 
ebs volumes, it can lock the volume for specific container? Going through the 
stateful set docs, the IP address itself is not guaranteed when container 
restarts, but it could get same hostname which is assigned by appending 
container number at the end of hostname.

2018-03-29 17:06:09 UTC - Sahaya Andrews Albert: So, thinking of scripting it 
around it's hostname and determine which pv's it should use. Is there a better 
approach we have than this?

2018-03-29 17:06:44 UTC - Matteo Merli: a persistent volume is assigned to a 
particular instance of the stateful set

2018-03-29 17:07:04 UTC - Matteo Merli: there should be nothing additional to 
be done

2018-03-29 17:14:00 UTC - Sahaya Andrews Albert: Does it retain both journal 
and ledger volumes?

2018-03-29 17:14:24 UTC - Matteo Merli: you need to have 2 volumes, though that 
should work

2018-03-29 17:15:14 UTC - Sahaya Andrews Albert: ok, What about the IP address? 
Should we use the hostname instead of IP?

2018-03-29 17:16:13 UTC - Matteo Merli: you can enable bookies to use hostname 
rather than IP to advertise

2018-03-29 17:16:20 UTC - Matteo Merli: that would be stable

2018-03-29 17:16:24 UTC - Sahaya Andrews Albert: ok

2018-03-29 17:17:15 UTC - Sahaya Andrews Albert: Thanks. I'll try it out.

2018-03-29 17:18:47 UTC - Sahaya Andrews Albert: Do you know if k8s has a 
config to get fully qualified host name? metadata.name doesn't append the 
domain name.

2018-03-29 17:20:18 UTC - Matteo Merli: You shouldn’t need that. Just pass 
`useHostNameAsBookieID=true` in bookie config

2018-03-29 17:20:27 UTC - Matteo Merli: 


2018-03-29 17:21:17 UTC - Sahaya Andrews Albert: Um... thats what I tried and 
saw zk still had ip's. Let me clean them up and retry.

2018-03-30 00:18:12 UTC - Matteo Merli: Hi @Rajan Dhabalia, I’m seeing some 
issues with the failure domain z-node creation

2018-03-30 00:19:14 UTC - Matteo Merli: it can create the failure domain z-node 
before the cluster z-node is created. This can happen when brokers are started 
while the initialization is still happening

2018-03-30 00:19:45 UTC - Matteo Merli: (which is typically the case when the 
initial cluster is deployed in kubernetes or similars)

2018-03-30 00:20:23 UTC - Matteo Merli: so it creates the 
`/admin/clusters/MY_CLUSTER/failureDomain` with the intermediate z-node paths

2018-03-30 00:21:25 UTC - Matteo Merli: problem is `/admin/clusters/MY_CLUSTER` 
gets created empty and then the `initialize-cluster-metadata` will fail because 
the z-node already exist, so the cluster metadata won’t be created properly

2018-03-30 00:26:06 UTC - Rajan Dhabalia: hmm.. so, probably we can avoid 
creating failure-domain if cluster is not created yet

2018-03-30 00:26:29 UTC - Rajan Dhabalia: let me take a look and I will create 
a PR

2018-03-30 00:27:28 UTC - Matteo Merli: thanks

2018-03-30 00:28:13 UTC - Matteo Merli: yes, I think we can try to do the 
regular zk create wihtouth the parent z-nodes creation

2018-03-30 00:28:56 UTC - Rajan Dhabalia: yes

2018-03-30 00:57:50 UTC - Jai Asher: I am planning to add 
`publishThrottlingRatePerTopicInMsg` and `publishThrottlingRatePerTopicInByte` 
to throttle publish rate per topic - similar to this PIP Rajan had worked on




Let me know if you see any issues with the suggestion

2018-03-30 01:04:24 UTC - Matteo Merli: Great, how do you plan to implement the 
throttling?

2018-03-30 01:33:07 UTC - Jai Asher: Due to ordering guarantees we can't error 
out the publish so I was thinking of either:-
- Closing the producer `PublishRateExceededException` using a new ProtoBuf 
Command which newer client versions honor.  - client does a backoff and 
reconnects
OR
 - setAutoRead off to create backpressure but then this will be a connection 
level throttling

2018-03-30 01:34:52 UTC - Matteo Merli:  client does a backoff and 
reconnects 

that’s not really controlled by server though

2018-03-30 01:35:23 UTC - Matteo Merli:  - setAutoRead off to create 
backpressure but then this will be a connection level throttling

True but I think this is the better option

2018-03-30 01:35:54 UTC - Matteo Merli: we should then schedule a task after, 
say 10ms and reevaluate the rate

2018-03-30 01:45:15 UTC - Rajan Dhabalia: but if we set `setAutoRead` off then 
isn't it impact all the topics on that connection even though other topics have 
not reached the limit?

2018-03-30 02:08:52 UTC - 

Slack digest for #dev - 2018-03-27

[Apache Pulsar Slack]

eceived error from server: Topic was already terminated'

2018-03-27 02:00:47 UTC - Igor Zubchenok: And you're right, no exception 
occurred if I close producer before terminating the topic.

2018-03-27 02:15:18 UTC - Igor Zubchenok: 1. here it is: 
<https://github.com/apache/incubator-pulsar/issues/1452>

2018-03-27 02:40:39 UTC - Igor Zubchenok: 2. One more thing I noted:
when I send several messages using a batch, I get the same ID for these 
messages.

2018-03-27 02:41:15 UTC - Igor Zubchenok: ```Producer producer = 
pulsarClient.createProducer(topicName, new ProducerConfiguration()
.setBatchingEnabled(true)
.setBatchingMaxMessages(1000)
.setBatchingMaxPublishDelay(1, TimeUnit.SECONDS)
);

producer.sendAsync("A".getBytes()).whenCompleteAsync((messageId, 
throwable) - {
System.out.println("A: " + messageId);
});
producer.sendAsync("B".getBytes()).whenCompleteAsync((messageId, 
throwable) - {
System.out.println("B: " + messageId);
});
```
output:
```
A: 1248:0:-1:0
B: 1248:0:-1:0
```

2018-03-27 02:47:17 UTC - Igor Zubchenok: While I read, I get another IDs:
```B: 1253:0:-1:0
A: 1253:0:-1:0
Read: 1253:0:-1:0
Read: 1253:0:-1:1```
Is it ok?

2018-03-27 02:54:56 UTC - Igor Zubchenok: Oops, sorry I used wrong slack 
channel today.

2018-03-27 03:01:04 UTC - Igor Zubchenok: 3. If I use a subscription and then 
user reconnects to another server instance, how can I continue using the the 
same user's subscription and cursor afterwards?

2018-03-27 03:16:57 UTC - Igor Zubchenok: I should just use the same name 
subscription name, right?

2018-03-27 03:26:57 UTC - Matteo Merli: Yes, exactly, it will resume from the 
last unackednmessage
+1 : Igor Zubchenok

2018-03-27 03:34:15 UTC - Igor Zubchenok: 4. You know, there is a lack of 
admin.persistentTopics().terminateTopic() method. I guess it should be there 
for completeness.

Slack digest for #dev - 2018-03-25

[Apache Pulsar Slack]

2018-03-24 17:36:39 UTC - Venkat: @Venkat has joined the channel

Slack digest for #dev - 2018-03-23

[Apache Pulsar Slack]

2018-03-22 15:40:54 UTC - Ivan Kelly: @Matteo Merli how is it that failed tests 
are rerun in pulsar?

2018-03-22 15:41:04 UTC - Ivan Kelly: i don't see the rerun stuff at all

2018-03-22 15:41:08 UTC - Ivan Kelly: in the pom

2018-03-22 16:12:24 UTC - Matteo Merli: It’s in the TestNG config, though it 
doesn’t seem to be really working

2018-03-22 16:12:41 UTC - Matteo Merli: since we’re using testNG it’s more 
complicated than with Junit

2018-03-22 16:12:49 UTC - Ivan Kelly: it's working enough to annoy me

2018-03-22 16:13:04 UTC - Ivan Kelly: for stuff like replicatortest, it uses a 
beforeClass and afterclass

2018-03-22 16:13:09 UTC - Ivan Kelly: so second run is dirty

2018-03-22 16:13:44 UTC - Matteo Merli: oh, I see

2018-03-22 16:14:29 UTC - Ivan Kelly: where is the testng file?

2018-03-22 16:14:36 UTC - Ivan Kelly: configuration i mean

2018-03-22 16:15:08 UTC - Matteo Merli: in `pulsar-broker/pom.xml` :

2018-03-22 16:15:11 UTC - Matteo Merli: ```
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
  properties
property
  namelistener/name
  
valueorg.apache.pulsar.tests.AnnotationListener/value
/property
  /properties
/configuration
  /plugin
```

2018-03-22 16:15:37 UTC - Matteo Merli: The retry is enabled only in few modules

2018-03-22 16:16:30 UTC - Ivan Kelly: ah

2018-03-22 16:16:41 UTC - Matteo Merli: I had another PR that was enabling 
everywhere, with auto test timeout, but still there were issues with the tests 
there: 

Slack digest for #dev - 2018-03-22

[Apache Pulsar Slack]

2018-03-21 23:19:46 UTC - Igor Zubchenok: @Igor Zubchenok has joined the channel

Slack digest for #dev - 2018-03-13

[Apache Pulsar Slack]

2018-03-13 02:58:05 UTC - Sijie Guo: @Masakazu Kitajo I completely forgot the 
jenkins stuff. sorry about that. I just added you to the hudson-jobadmin group, 
you should be able to access it now

Slack digest for #dev - 2018-03-09

[Apache Pulsar Slack]

2018-03-08 14:46:34 UTC - Masakazu Kitajo: Seems like this job has been running 
for 8 days.


2018-03-08 14:47:03 UTC - Masakazu Kitajo: Can anybody stop it?

2018-03-08 14:49:41 UTC - Masakazu Kitajo: or, can anybody give me an access to 
Jenkins?

2018-03-08 15:05:09 UTC - Ivan Kelly: killed

2018-03-08 15:05:29 UTC - Ivan Kelly: i think you have to ask infra for access

2018-03-08 15:06:02 UTC - Masakazu Kitajo: yeah, but the infra docs says ask 
PMC chair first

2018-03-08 15:06:57 UTC - Masakazu Kitajo: 


2018-03-08 15:08:39 UTC - Ivan Kelly: oh, maybe actually

2018-03-08 17:00:02 UTC - Matteo Merli: Yes, problem is our case it should be 
the IPMC chair

2018-03-08 21:08:00 UTC - Masakazu Kitajo: Should I get the access from OUR 
(I)PMC chair? I thought any PMC chairs can grant it.

2018-03-08 21:08:38 UTC - Sijie Guo: I can help

2018-03-08 21:08:58 UTC - Sijie Guo: What is your Apache id

2018-03-08 21:09:14 UTC - Masakazu Kitajo: Thanks! It’s maskit.

2018-03-08 21:09:55 UTC - Sijie Guo: Okay give me one hr. I will get to a 
laptop and do it.

2018-03-08 21:10:20 UTC - Masakazu Kitajo: Thank you. no rush.

2018-03-08 23:08:31 UTC - eren avsarogullari: @eren avsarogullari has joined 
the channel

Slack digest for #dev - 2018-03-01

[Apache Pulsar Slack]

2018-03-01 00:49:07 UTC - Sahaya Andrews Albert: Good to hear @Matteo Merli. We 
could target it for 2.0 release?

2018-03-01 00:49:29 UTC - Matteo Merli: It’s **merged**

2018-03-01 00:50:05 UTC - Matteo Merli: Pulsar master is already using 
BookKeeper-4.7.0-SNAPSHOT

2018-03-01 00:50:25 UTC - Matteo Merli: BookKeeper-4.7.0 will be released soon

2018-03-01 00:51:24 UTC - Matteo Merli: the idea is start testing it out 
earlier, before approaching the release

2018-03-01 00:51:31 UTC - Matteo Merli: (Pulsar release 2.0)

2018-03-01 00:51:52 UTC - Sahaya Andrews Albert: I see, but did the release 
candidate go out with that version as well?

2018-03-01 00:55:12 UTC - Matteo Merli: No no, the release candidate is for 
Pulsar 1.22 — Master has already moved to 2.0-SNAPSHOT

2018-03-01 00:56:22 UTC - Sahaya Andrews Albert: Got it, thanks

2018-03-01 01:02:50 UTC - Matteo Merli: :beers:

2018-03-01 08:14:03 UTC - Sijie Guo: any committers around? can I get a review 
on this -  (fixing a typo)

2018-03-01 08:31:11 UTC - Jai Asher: Please download, test and vote "Pulsar 
1.22.0-incubating Release Candidate 3" 
This time it for 
 mailing list

Slack digest for #dev - 2018-02-27

[Apache Pulsar Slack]

2018-02-27 02:18:07 UTC - Anil Muppalla: @Anil Muppalla has joined the channel

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

2018-02-22 09:10:30 UTC - Jai Asher: Please try and find time to download, test 
and vote for "Pulsar 1.22.0-incubating Release Candidate 3"

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro
+1 : Jai Asher

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-22

[Apache Pulsar Slack]

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo, Lewis Kaneshiro

Slack digest for #dev - 2018-02-21

[Apache Pulsar Slack]

2018-02-21 02:56:20 UTC - Jai Asher: Looks like we may need another release 
candidate with this fix included 


2018-02-21 03:01:00 UTC - Matteo Merli: Yes, that could cause failure at 
unexpected times

2018-02-21 21:13:24 UTC - David Fisher: PIP-15 looks really cool
blush : Sijie Guo
fire : Sijie Guo

Slack digest for #dev - 2018-02-20

[Apache Pulsar Slack]

2018-02-20 18:42:47 UTC - Anil Muppalla: @Anil Muppalla has joined the channel

Slack digest for #dev - 2018-02-12

[Apache Pulsar Slack]

2018-02-11 21:54:11 UTC - Masakazu Kitajo: I mean general coding hygiene. 
Thanks.

2018-02-12 17:47:55 UTC - Dave Rusek: thank you!

2018-02-12 17:49:09 UTC - Dave Rusek: I would really like to refactor the 
ServerCnx and ClientCnx into methods that aren't hundreds or lines long and 
nested a dozen levels deep :smile: