Re: [VOTE] Maintaining "Apache Pulsar" name

[Jia Zhai]

+1 for keeping "Apache Pulsar"

On Thu, Jun 21, 2018 at 9:18 AM, Sijie Guo  wrote:

> +1 for keeping "Apache Pulsar"
>
> On Wed, Jun 20, 2018 at 5:06 PM Matteo Merli  wrote:
>
> > Following the previous discussion at
> >
> > https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf977
> 2677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E
> > I am calling a formal vote for keep using "Apache Pulsar" name for the
> > project.
> >
> > This vote will be open for at least 72 hours. After that we will
> > communicate the decision to trademarks@apache
> >
> > +1 from me
> >
> > Matteo
> > --
> > Matteo Merli
> > 
> >
>

Re: [VOTE] Maintaining "Apache Pulsar" name

[Sijie Guo]

+1 for keeping "Apache Pulsar"

On Wed, Jun 20, 2018 at 5:06 PM Matteo Merli  wrote:

> Following the previous discussion at
>
> https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf9772677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E
> I am calling a formal vote for keep using "Apache Pulsar" name for the
> project.
>
> This vote will be open for at least 72 hours. After that we will
> communicate the decision to trademarks@apache
>
> +1 from me
>
> Matteo
> --
> Matteo Merli
> 
>

Re: [VOTE] Maintaining "Apache Pulsar" name

[Sanjeev Kulkarni]

+1 for keep using “Apache Pulsar”

On Wed, Jun 20, 2018 at 5:06 PM Matteo Merli  wrote:

> Following the previous discussion at
>
> https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf9772677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E
> I am calling a formal vote for keep using "Apache Pulsar" name for the
> project.
>
> This vote will be open for at least 72 hours. After that we will
> communicate the decision to trademarks@apache
>
> +1 from me
>
> Matteo
> --
> Matteo Merli
> 
>

RE: [VOTE] Maintaining "Apache Pulsar" name

[Nozomi Kurihara]

+1 for keep using "Apache Pulsar"


Regards,

Nozomi


差出人: Matteo Merli 
送信日時: 2018年6月21日 9:06:42
宛先: dev@pulsar.incubator.apache.org
件名: [VOTE] Maintaining "Apache Pulsar" name

Following the previous discussion at
https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf9772677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E
I am calling a formal vote for keep using "Apache Pulsar" name for the
project.

This vote will be open for at least 72 hours. After that we will
communicate the decision to trademarks@apache

+1 from me

Matteo
--
Matteo Merli

Re: [VOTE] Maintaining "Apache Pulsar" name

[Ali Ahmed]

+1 for keeping "Apache Pulsar"

-Ali

On Wed, Jun 20, 2018 at 5:26 PM, Rajan Dhabalia 
wrote:

> +1 for "Apache Pulsar"
>
> Thanks,
> Rajan
>
> On Wed, Jun 20, 2018 at 5:06 PM, Matteo Merli  wrote:
>
> > Following the previous discussion at
> > https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf977
> > 2677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E
> > I am calling a formal vote for keep using "Apache Pulsar" name for the
> > project.
> >
> > This vote will be open for at least 72 hours. After that we will
> > communicate the decision to trademarks@apache
> >
> > +1 from me
> >
> > Matteo
> > --
> > Matteo Merli
> > 
> >
>

[VOTE] Maintaining "Apache Pulsar" name

[Matteo Merli]

Following the previous discussion at
https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf9772677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E
I am calling a formal vote for keep using "Apache Pulsar" name for the
project.

This vote will be open for at least 72 hours. After that we will
communicate the decision to trademarks@apache

+1 from me

Matteo
-- 
Matteo Merli

Jenkins build is back to stable : pulsar-master #547

[Apache Jenkins Server]

See 

Re: Non-serializable builders

[Sijie Guo]

Hi Geoffroy,

I put up a PR https://github.com/apache/incubator-pulsar/pull/2004 for
addressing the issue. If you can take a look and see if that approach
addresses your problem.

- Sijie

On Fri, Jun 8, 2018 at 8:32 AM Sijie Guo  wrote:

> Hi Geoffroy,
>
> I created an issue for
> https://github.com/apache/incubator-pulsar/issues/1943.
>
> We will address it for the upcoming 2.1 release.
>
> - Sijie
>
> On Fri, Jun 8, 2018 at 6:39 AM Geoffroy Fouquier <
> geoffroy.fouqu...@exensa.com> wrote:
>
>> On 08/06/2018 12:01, Sijie Guo wrote:
>> > Geoffroy,
>> >
>> > Thank you for reporting this. The change was made to evolve pulsar into
>> a
>> > type-safe client with schema and more validations. Along with the idea,
>> > we changed the client to become a more fluent style builder and hide the
>> > configuration data as an implementation detail to the pulsar client
>> > implementation.
>> >
>> > However we missed the use cases in data computing world, people tends to
>> > use java Serializable on sharing configuration.
>> >
>> > We would incorporate your use cases and try to bring the configuration
>> > object back.
>> >
>> > - Sijie
>>
>> That would be great, thanks!
>>
>> >
>> >
>> > On Fri, Jun 8, 2018 at 1:09 AM Geoffroy Fouquier <
>> > geoffroy.fouqu...@exensa.com> wrote:
>> >
>> >> We are using pulsar 1.22 within a spark framework and I am currently
>> >> upgrading my cluster to pulsar 2.0. One of the main change concerns the
>> >> configuration classes, replace by builders. Although ProducerBuilder
>> and
>> >> ConsumerBuilder interfaces implement Serializable, corresponding
>> >> implementations aren't, because a pulsar client object is embedded. The
>> >> schema object is also a problem for serialization.
>> >>
>> >>
>> >> Basically, with 1.22 my producer app. instanciate a client and a
>> >> producer on each executor and only configurations classes need to be
>> >> serialized
>> >>
>> >> ---8<---
>> >>
>> >> WarcRecordExtractor
>> >>   .load(sc, input)
>> >>   .foreachPartition{ ite =>
>> >>
>> >>   val client = PulsarClient.create(ServiceUrl, clientConf)
>> >>   val producer = client.createProducer(topic, producerConf)
>> >>   ite.foreach{ x => producer.sendAsync(x._2.content) }
>> >>   producer.close()
>> >>
>> >>   client.close()
>> >>
>> >>   }
>> >>
>> >> ---8<---
>> >>
>> >>
>> >> With 2.0 I try to replace the configuration classes with the
>> >> corresponding builders, but this setting doesn't work since the
>> >> producerBuilder isn't serializable :
>> >>
>> >> ---8<---
>> >>
>> >>   [...]
>> >>
>> >>   val client = clientBuilder.serviceUrl(serviceUrl).build()
>> >>   val producer = producerBuilder.topic(topicName).create
>> >>
>> >>   [...]
>> >>
>> >> ---8<---
>> >>
>> >>
>> >> My actual workaround is to rewrite my own ProducerBuilderImpl without
>> >> pulsar client or schemas (the createAsync method still exists but throw
>> >> an exception). And then to instanciate a producer like this :
>> >>
>> >> ---8<---
>> >>
>> >>   [...]
>> >>
>> >>   val client : PulsarClientImpl =
>> >> clientBuilder.serviceUrl(broker).build().asInstanceOf[PulsarClientImpl]
>> >>   val producer =
>> >> client.createProducerAsync(producerBuilder.topic(topic).getConf(),
>> >> org.apache.pulsar.client.api.Schema.BYTES).get()
>> >>
>> >>   [...]
>> >>
>> >> ---8<---
>> >>
>> >> where producerBuilder is my own implementation which implements
>> >> ProducerBuilder interface.
>> >>
>> >>
>> >> I did the same thing for ConsumerBuilderImpl and also rewrite
>> >> SparkStreamingPulsarReceiver with the same kind of workaround. I don't
>> >> know why the configuration classes have been replaced by builders, but
>> >> it became more difficult to use it with spark (and probably with other
>> >> distributed framework), but maybe i did it wrong.
>> >>
>> >>
>> >>
>> >>
>>
>>

Re: [ANNOUNCE] Apache BookKeeper 4.7.1 released

[Jia Zhai]

Cong~ . Thanks for the work @Sijie.

On Thu, Jun 21, 2018 at 1:24 AM, Enrico Olivelli 
wrote:

> Great! Thank you Sijie
>
> Enrico
>
>
> Il mer 20 giu 2018, 17:31 Sijie Guo  ha scritto:
>
>> The Apache BookKeeper team is proud to announce Apache BookKeeper version
>> 4.7.1.
>>
>> Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage
>> service optimized for
>> real-time workloads. It has been used for a fundamental service to build
>> reliable services.
>> It is also the log segment store for Apache DistributedLog and the message
>> store for Apache Pulsar.
>>
>> This is the 11th release of Apache BookKeeper.
>>
>> This is a bugfix release, which fixes a bunch of issues reported from
>> users of 4.7.0.
>> These changes include bug fixes around ledger cache and object pooling,
>> performance
>> enhancement avoid memory copies and various bug fixes and improvements
>> around
>> bookkeeper table service.
>>
>> For BookKeeper release details and downloads, visit:
>>
>> https://bookkeeper.apache.org/releases/
>>
>> BookKeeper 4.7.1 Release Notes are at:
>>
>> https://bookkeeper.apache.org/docs/4.7.1/overview/releaseNotes/
>>
>> We would like to thank the contributors that made the release possible.
>>
>> Regards,
>>
>> The BookKeeper Team
>>
> --
>
>
> -- Enrico Olivelli
>

Jenkins build became unstable: pulsar-master #546

[Apache Jenkins Server]

See 

[ANNOUNCE] Apache BookKeeper 4.7.1 released

[Sijie Guo]

The Apache BookKeeper team is proud to announce Apache BookKeeper version
4.7.1.

Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage
service optimized for
real-time workloads. It has been used for a fundamental service to build
reliable services.
It is also the log segment store for Apache DistributedLog and the message
store for Apache Pulsar.

This is the 11th release of Apache BookKeeper.

This is a bugfix release, which fixes a bunch of issues reported from users
of 4.7.0.
These changes include bug fixes around ledger cache and object pooling,
performance
enhancement avoid memory copies and various bug fixes and improvements
around
bookkeeper table service.

For BookKeeper release details and downloads, visit:

https://bookkeeper.apache.org/releases/

BookKeeper 4.7.1 Release Notes are at:

https://bookkeeper.apache.org/docs/4.7.1/overview/releaseNotes/

We would like to thank the contributors that made the release possible.

Regards,

The BookKeeper Team

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.

Jenkins build is back to stable : pulsar-master #543

[Apache Jenkins Server]

See 

Re: Non-persistent topics

[Sijie Guo]

2.1.0-SNAPSHOT is published to apache staging nightly.

I will try to include this fix for 2.1.0 release in this week. So it can go
out with 2.1 release.

On Tue, Jun 19, 2018 at 11:40 PM Geoffroy Fouquier <
geoffroy.fouqu...@exensa.com> wrote:

> On 19/06/2018 21:58, Sijie Guo wrote:
> > I put up a fix - https://github.com/apache/incubator-pulsar/pull/1994
> > verified that it fixes the problem. however I would like to get feedback
> > before I added unit tests / integration tests.
> >
> > - Sijie
>
> Great, thanks !
>
> Is there some nightly build which produces binary distribution ?
>
>

Re: Non-persistent topics

[Geoffroy Fouquier]

On 19/06/2018 21:58, Sijie Guo wrote:

I put up a fix - https://github.com/apache/incubator-pulsar/pull/1994
verified that it fixes the problem. however I would like to get feedback
before I added unit tests / integration tests.

- Sijie


Great, thanks !

Is there some nightly build which produces binary distribution ?