Sam

Your last example will send one at a time. You can sendAsync then collect all the futures using .sequence and then await on that.

I assume you're not adding pulsar4s-circe to your build? On Mon, 14 Dec 2020 at 12:13, Colin Bester wrote: > I am using the jackson dependency in my sbt file...

I can't see anything in the jackson module that would pull it down. On Mon, 14 Dec 2020 at 12:16, Stephen Samuel (Sam) wrote: > I assume you're not adding...

Ok here we are, it's nothing to do with the Scala Circe json library, but this https://github.com/trevorr/circe Which I assume pulsar itself is using. On Mon, 14 Dec 2020 at...

Yep. I'd imagine it's looking for the JNI version and falling back. Hadoop and Avro do similar things for other JNI libraries. On Mon, 14 Dec 2020 at 12:23, Colin...

I agree with Greg. We should be either all in on Try or just use exceptions. Really I should have called these methods dosomethingUnsafe and then dosomething() returns a Try....

I don't think we should break all the methods now was kind of what I was meaning unless it was a 3.0 release, but then we need pulsar to do...

Yes, I will do this for the 2.0.0 release I am working on. Good idea.

Maybe we can be more conservative by saying we only upgrade a dependency by patch version for any given minor version ? In other words for 2.4.x we only update...

Agreed. On Thu, 23 Jan 2020 at 20:43, Greg Methvin wrote: > I actually think we can be more conservative than that if possible. For > example Akka 2.6.x is...