Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Jia Zhai 
+1  (non-binding)

Best Wishes.


On Thu, Sep 13, 2018 at 4:49 AM sebb  wrote:

> On 12 September 2018 at 16:40, Dave Fisher  wrote:
> > Hi -
> >
> > The Apache Pulsar project is ready to graduate as a TLP. They entered
> > Incubation on June 1, 2017, have had many releases and have grown the
> > community.
> >
> > Vote:
> > [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> > [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
> >
> > At the mentors request they did a maturity model analysis [1] and wrote
> > contribution guidelines. [2]
> >
> > The Graduation Proposal was written and discussed on the dev list. [3] At
> > the mentor's recommendation the By-Laws Clause was removed.
> >
> > The new prospective PMC is set and the VOTE thread in the podling is here
> > [4] with these results. [5]
> >
> > Regards,
> > Dave
> >
> > [1]
> >
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> > [2] http://pulsar.incubator.apache.org/en/contributing/
> > [3]
> >
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> > [4]
> >
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> > [5]
> >
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
> >
> >
> > 
> >
> > Establish the Apache Pulsar Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub and queue semantics over
> > topics, lightweight compute framework, automatic cursor management for
> > subscribers, and cross-datacenter replication.
>
> Such detail as provided in the last sentence is unusual for graduation
> resolutions.
> I think the last sentence should be dropped from the resolution; it's
> not necessary.
>
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> > for the creation and maintenance of software related to a highly
> > scalable, low latency messaging platform running on commodity hardware.
> > It provides simple pub-sub and queue semantics over topics, lightweight
> > compute framework, automatic cursor management for subscribers, and
> > cross-datacenter replication; and be it further
>
> Ditto
>
> > RESOLVED, that the office of "Vice President, Apache Pulsar" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache Pulsar
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Pulsar
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache Pulsar Project:
> >
> > * Boyang Jerry Peng 
> > * Brad McMillen 
> > * David Fisher 
> > * Francis Christopher Liu 
> > * Hiroyuki Sakai 
> > * Ivan Brendan Kelly 
> > * Jai Asher 
> > * Jia Zhai 
> > * Jim Jagielski 
> > * Joe Francis 
> > * Ludwig Pummer 
> > * Masahiro Sakamoto 
> > * Masakazu Kitajo 
> > * Matteo Merli 
> > * Nozomi Kurihara 
> > * P. Taylor Goetz 
> > * Rajan Dhabalia 
> > * Sahaya Andrews 
> > * Sanjeev Kulkarni 
> > * Sebastián Schepens 
> > * Siddharth Boobna 
> > * Sijie Guo 
> > * Yuki Shiga 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> > to the office of Vice President, Apache Pulsar, to serve in accordance
> > with and subject to the direction of the Board of Directors and the
> > Bylaws of the Foundation until death, resignation, retirement, removal
> > or disqualification, or until a successor is appointed; and be it
> > further
> >
> > RESOLVED, that the Apache Pulsar Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Pulsar
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
>

Re: [DRAFT] [UPDATED] Graduation resolution proposal

2018-09-04 Thread Jia Zhai 
+1.

I am honored to be asked to be on the PMC. Please keep me on the list. ：）

On Tue, Sep 4, 2018 at 2:47 PM Hiroyuki Sakai  wrote:

> +1
>
> I would like to be part of PMC.
>
> Hiroyuki
>
>
> -Original Message-
> From: Masahiro Sakamoto 
> Reply-To: "dev@pulsar.incubator.apache.org" <
> dev@pulsar.incubator.apache.org>
> Date: Tuesday, September 4, 2018 15:43
> To: "dev@pulsar.incubator.apache.org" 
> Subject: RE: [DRAFT] [UPDATED] Graduation resolution proposal
>
> +1
>
> I would like to be part of PMC.
>
> --
> Masahiro Sakamoto
> Yahoo Japan Corp.
> E-mail: massa...@yahoo-corp.jp
> --
>
> > -Original Message-
> > From: Nozomi Kurihara [mailto:nkuri...@yahoo-corp.jp]
> > Sent: Tuesday, September 04, 2018 2:27 PM
> > To: dev@pulsar.incubator.apache.org
> > Subject: RE: [DRAFT] [UPDATED] Graduation resolution proposal
> >
> > +1
> >
> > And would like to be part of PMC.
> >
> >
> > Nozomi
> >
> > 
> > 差出人: Ivan Kelly 
> > 送信日時: 2018年9月3日 16:38:41
> > 宛先: dev@pulsar.incubator.apache.org
> > 件名: Re: [DRAFT] [UPDATED] Graduation resolution proposal
> >
> > +1
> >
> > I wish to remain part of PMC.
> >
> > Regarding BookKeeper bylaws, BookKeeper has them because ZooKeeper
> had them
> > when we branched off, and my understanding is that zookeeper had
> them,
> > because hadoop had them when they branched off. As far as I'm
> concerned,
> > they're unnecessary given the default asf bylaws, but that's a
> discussion
> > for another list.
> >
> > -Ivan
> >
> > On Sun, Sep 2, 2018 at 10:36 PM, P. Taylor Goetz 
> wrote:
> > > +1
> > >
> > > -Taylor
> > >
> > >> On Sep 2, 2018, at 3:18 PM, Matteo Merli 
> wrote:
> > >>
> > >> Updated the initial draft by removing paragraph on the "have a
> > >> tasking for creating set of bylaws".
> > >>
> > >> 
> > >>
> > >> Establish the Apache Pulsar Project
> > >>
> > >> WHEREAS, the Board of Directors deems it to be in the best
> interests
> > >> of the Foundation and consistent with the Foundation's purpose to
> > >> establish a Project Management Committee charged with the creation
> > >> and maintenance of open-source software, for distribution at no
> > >> charge to the public, related to a highly scalable, low latency
> > >> messaging platform running on commodity hardware. It provides
> simple
> > >> pub-sub and queue semantics over topics, lightweight compute
> > >> framework, automatic cursor management for subscribers, and
> > cross-datacenter replication.
> > >>
> > >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee
> > >> (PMC), to be known as the "Apache Pulsar Project", be and hereby
> is
> > >> established pursuant to Bylaws of the Foundation; and be it
> further
> > >>
> > >> RESOLVED, that the Apache Pulsar Project be and hereby is
> responsible
> > >> for the creation and maintenance of software related to a highly
> > >> scalable, low latency messaging platform running on commodity
> hardware.
> > >> It provides simple pub-sub and queue semantics over topics,
> > >> lightweight compute framework, automatic cursor management for
> > >> subscribers, and cross-datacenter replication; and be it further
> > >>
> > >> RESOLVED, that the office of "Vice President, Apache Pulsar" be
> and
> > >> hereby is created, the person holding such office to serve at the
> > >> direction of the Board of Directors as the chair of the Apache
> Pulsar
> > >> Project, and to have primary responsibility for management of the
> > >> projects within the scope of responsibility of the Apache Pulsar
> > >> Project; and be it further
> > >>
> > >> RESOLVED, that the persons listed immediately below be and hereby
> are
> > >> appointed to serve as the initial members of the Apache Pulsar
> Project

Re: PIP 22 : Pulsar Dead Letter Topic

2018-08-10 Thread Jia Zhai 


On Sat, Aug 11, 2018 at 2:43 AM, Sijie Guo  wrote:

> Thank you Penghui.
>
> I have also created the wiki page for this PIP.
>
> https://github.com/apache/incubator-pulsar/wiki/PIP-22:-
> Pulsar-Dead-Letter-Topic
>
> - Sijie
>
> On Fri, Aug 10, 2018 at 5:37 AM 李鹏辉gmail  wrote:
>
> > Dear all
> >
> > This is a PIP to add feature of Dead Letter Topic to control the message
> > redelivery behavior by users. If the delivery times, which was tracked in
> > Redelivery Tracker, reached user defined threshold, we re-deliver the
> > message to Dead Letter Topic, then mark the message acked in original
> > subscription.
> >
> >
> > https://docs.google.com/document/d/1ClfrGg87nihlrHVyeSwfXgoM6Qx3F
> njcx5bJsnEcWO4/edit?usp=sharing
> >
> > —
> > Regards,
> > Penghui Li
>

Re: [Discuss] Blog at pulsar website

2018-08-04 Thread Jia Zhai 
+1  

On Sat, Aug 4, 2018 at 7:14 AM, Sijie Guo  wrote:

> As discussed, I try to enable the blog in pulsar website and have one
> example for 2.1.0 release. The idea is to have a channel (e.g. rss feeds)
> in Pulsar website for users to catch up latest information in Pulsar.
>
> https://github.com/apache/incubator-pulsar/pull/2308
>
> Let me know how do you guys think.
>
> - Sijie
>
> On Tue, Jun 26, 2018 at 11:46 PM Nozomi Kurihara 
> wrote:
>
> > Hi,
> >
> >
> > I think it is good idea to have blogs/news at pulsar website since users
> > can easily catch up latest information.
> >
> >
> > Regards,
> >
> > Nozomi
> >
> > 
> > 差出人: Sijie Guo 
> > 送信日時: 2018年6月27日 15:33:55
> > 宛先: dev@pulsar.incubator.apache.org
> > 件名: [Discuss] Blog at pulsar website
> >
> > Hi,
> >
> > Do you think it is worth having a blogs (or news) category at pulsar
> > website, for publishing news about releases or even blogs about new
> > features?
> >
> > I see quite a lot of projects are doing so, for example:
> >
> > Arrow: http://arrow.apache.org/blog/
> > Beam: https://beam.apache.org/blog/
> > RocketMQ: https://rocketmq.apache.org/year-archive/
> >
> > Both Arrow and Beam started publishing blog posts since they were in
> > incubator.
> >
> > https://beam.apache.org/beam/release/2016/06/15/first-release.html
> > https://rocketmq.apache.org/rocketmq/filter-messages-by-
> sql92-in-rocketmq/
> >
> >
> > Thoughts?
> >
> > - Sijie
> >
>

Re: [ANNOUNCE] Apache Pulsar 2.1.0-incubating released

2018-08-04 Thread Jia Zhai 
Con~. Thanks a lot for the great work.

On Sat, Aug 4, 2018 at 2:14 AM, Sijie Guo  wrote:

> The Apache Pulsar team is proud to announce Apache Pulsar version
> 2.1.0-incubating.
>
> This is the seventh Pulsar release after entering the Apache Incubator.
>
> Pulsar is a highly scalable, low latency messaging streaming platform
> running on
> commodity hardware. It provides simple pub/sub semantics over topics,
> supports
> at-least-once and effectively-once delivery of messages, automatic cursor
> management
> for subscribers, and multi-tenancy and cross-datacenter replication.
> Additionally,
> it also provides lightweight stream native processing through Pulsar
> Functions.
>
> 2.1.0-incubating release introduces several major features and improvements
> from many contributors. These major features include:
>
> - Pulsar IO : A
> serverless inspired connector framework for moving data in and out of
> Apache Pulsar leveraging Pulsar Functions
> . 6
> builtin connectors are included: Kafka
> , Kinesis
> , RabbitMQ
> , Aerospike
> , Cassandra
>  and Twitter
> Firehose .
>
> - Tiered Storage
> : An
> offloading mechanism in Pulsar segment store to offload old segments from
> Apache BookKeeper into long term storage such as HDFS, S3, GCS. S3 is
> currently supported in this release.
>
> - Stateful Function
> : Pulsar
> Functions introduces a new State API
>  to store
> function state back to Apache BookKeeper. It is a deep integration with
> BookKeeper's table service and it will simplify developing stateful
> applications using Pulsar Functions. It is available as a developer-preview
> feature in Java SDK.
>
> - Go Client
> : A cgo
> wrapper over existing c++ client.
>
> - More Schemas are introduced, including Avro
>  incubating/pulsar-client-schema/src/main/java/org/
> apache/pulsar/client/impl/schema/AvroSchema.java>
> and Protobuf
>  incubating/pulsar-client-schema/src/main/java/org/
> apache/pulsar/client/impl/schema/ProtobufSchema.java>
> .
>
>
> For Pulsar release details and downloads, visit:
>
> https://pulsar.incubator.apache.org/download
>
> Release Notes are at:
> http://pulsar.apache.org/release-notes/#2.1.0-incubating
>
> We would like to thank the contributors that made the release possible.
>
> Regards,
>
> The Pulsar Team
>
> DISCLAIMER:
> Apache Pulsar is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
> required of all newly accepted projects until a further review indicates
> that
> the infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects. While
> incubation status is not necessarily a reflection of the completeness or
> stability
> of the code, it does indicate that the project has yet to be fully endorsed
> by the ASF.
>

Re: [ANNOUNCE] github.com/Comcast/pulsar-client-go

2018-08-01 Thread Jia Zhai 
, Great work.

On Wed, Aug 1, 2018 at 7:43 AM, Adam Williams  wrote:

> > the starting point would be making the interface consistent across these
> two clients
>
> I agree this is a good goal and understand the desire for consistency,
> although I'm not sure that 100% parity would make sense given the
> current interface. Definitely naming can be changed to match the cgo
> client whenever possible, eg Client.NewProducer vs
> Client.CreateProducer (note that the C++ and Java clients differ
> here). Some things though may not translate nicely into the native Go
> client, such as ClientOptions.IOThreads, since Go does not directly
> expose OS threads. And then there are design decisions that would be
> worth discussing, such as having a global client timeout for certain
> operations (ClientOptions.OperationTimeoutSeconds) versus using
> context.Context for operation cancelation/timeouts at the method
> level.
>
> Maybe there can be a more minimal interface both clients satisfy while
> allowing each to provide custom functionalities? Another goal worth
> considering is consistent behavior between this client and the others
> (Java, C++).
>
>
>
>
>
> On Mon, Jul 30, 2018 at 7:19 PM Sijie Guo  wrote:
> >
> > Awesome work, Adam! It is really great to see a native go client under
> > development. It will be interesting to discuss a plan how to consolidate
> > the native go client and cgo client. probably one of the starting point
> > would be making the interface consistent across these two clients.
> >
> > - Sijie
> >
> >
> > On Mon, Jul 30, 2018 at 2:44 PM Adam Williams 
> wrote:
> >
> > > Hello,
> > >
> > > I'd like to announce a newly released Go client library for Pulsar:
> > > https://github.com/Comcast/pulsar-client-go.
> > >
> > > The client follows semantic versioning and as of today is tagged at
> > > v0.1.0. This indicates that it is unstable and that breaking changes
> are
> > > allowed (up until the v1.x release) and should be expected.
> > >
> > > There is already a Go client included in the official Pulsar repository
> > > (under /pulsar-client-go directory). It is a wrapper around the C++
> > > library. As such, cgo must be used when compiling. In contrast, this
> newly
> > > released client is 100% Go. This is the main reason it was open
> sourced, as
> > > we hope a 100% Go client will be a valuable addition to the Pulsar
> > > ecosystem since it avoids the complications associated with wrapping a
> C++
> > > library.
> > >
> > > We'd like to invite collaborators to help with the development of this
> > > library. The README lists steps to start contributing, goals, and also
> some
> > > of the major known deficiencies of the library. In addition to this
> mailing
> > > list, we propose that Github issues be used to coordinate efforts and
> track
> > > bugs and feature development.
> > >
> > > We hope this contribution is an additive one and look forward to
> working
> > > with the community to bring it up to par with the other client
> libraries.
> > >
>

Re: PIP 18: Pulsar SQL

2018-07-22 Thread Jia Zhai 


On Sat, Jul 21, 2018 at 2:12 AM, Dave Fisher  wrote:

> OK. Nice discussion.
>
> It would be helpful if the disposition of the PIP-18 were stated at the
> top along with references to the closed PR discussions.
>
> Thanks,
> Dave
>
> > On Jul 20, 2018, at 9:21 AM, Joe F  wrote:
> >
> > I think 'rejected' is perhaps a misnomer.  That PIP-18 was made redundant
> > in  favor of enhancing connectors,  which was in concurrent development
> at
> > that time.  This was discussed, and the  discussion is on the PR threads
> > for PIP-18 at  https://github.com/apache/incubator-pulsar/pull/1594 and
> > https://github.com/apache/incubator-pulsar/issues/1582
> >
> > Joe
> >
> >
> > On Fri, Jul 20, 2018 at 8:05 AM, Dave Fisher 
> wrote:
> >
> >> Hi -
> >>
> >> I don’t see a decision made on list to reject any PIP-18? Where was that
> >> decision made?
> >>
> >> Regards,
> >> Dave
> >>
> >>> On Jul 19, 2018, at 10:09 PM, Sijie Guo  wrote:
> >>>
> >>> Yeah we should. it might be good to add "Next PIP number" to  the main
> >> page?
> >>>
> >>> On Thu, Jul 19, 2018 at 10:02 PM Jerry Peng <
> jerry.boyang.p...@gmail.com
> >>>
> >>> wrote:
> >>>
>  Ok I will update the PIP number.  We should probably still list the
> >> reject
>  PIP on the wiki with the other PIPs.  How else will we know what the
> >> latest
>  number is.
> 
>  Best,
> 
>  Jerry
> 
>  On Thu, Jul 19, 2018 at 9:54 PM Sijie Guo  wrote:
> 
> > This is a good catch!
> >
> > @Jerry Peng  We need to change this to
> PIP-19.
> >
> > PIP-18 Replicator is actually rejected in favor of using Pulsar I/O
> > connector. we should still list in the PIP list but mark it as
> >> Rejected.
> >
> > Thoughts?
> >
> > - Sijie
> >
> > On Thu, Jul 19, 2018 at 9:32 PM Dave Fisher 
>  wrote:
> >
> >> Replicator -
> >>
> >
>  https://github.com/apache/incubator-pulsar/wiki/PIP-18:-
> >> Pulsar-Replicator
> >>
> >> Sent from my iPhone
> >>
> >>> On Jul 19, 2018, at 4:20 PM, Jerry Peng <
> jerry.boyang.p...@gmail.com
> >
> >> wrote:
> >>>
> >>> Hi Dave,
> >>>
> >>> What do you mean by two PIP-18s? Is there a another PIP-18? I can't
> > seem
> >> to
> >>> find another PIP tagged as 18.
> >>>
> >>> Best,
> >>>
> >>> Jerry
> >>>
>  On Thu, Jul 19, 2018 at 4:08 PM Dave Fisher <
> dave2w...@comcast.net>
> >> wrote:
> 
>  Hi -
> 
>  Interesting extension. It looks like there are two PIP-18s.
> 
>  Regards,
>  Dave
> 
> > On Jul 19, 2018, at 12:44 PM, Jerry Peng <
> > jerry.boyang.p...@gmail.com>
>  wrote:
> >
> > Hi everyone,
> >
> > I have added a PIP for adding a SQL querying layer for Pulsar by
>  leveraging
> > Presto to allow users to query data in topics.  The link to the
>  PIP:
> >
> > https://github.com/apache/incubator-pulsar/wiki/PIP-18:-
> Pulsar-SQL
> >
> > Please read the document. Any feedback or suggestions is
> valuable!
> >
> > Best,
> >
> > Jerry
> 
> 
> >>
> >
> 
> >>
> >>
>
>

Re: [VOTE] Maintaining "Apache Pulsar" name

2018-06-20 Thread 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: [ANNOUNCE] Apache BookKeeper 4.7.1 released

2018-06-20 Thread 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
>

Re: triage labels

2018-06-14 Thread Jia Zhai 
 count me on it

On Thu, Jun 14, 2018 at 7:13 AM, Sijie Guo  wrote:

> Hi all,
>
> Ivan and me started the idea of doing bug triages on pulsar github issues,
> to make sure we don't miss any issues reported from users at mailing list
> or slack channel and make sure every issue is helped. We are using
> `triage/week-` to label the issues. so if you are seeing such labels,
> don't be freaked out about that :)
>
> if you volunteer to help and contribute to issue triages, feel free to ping
> Ivan and me as well :)
>
> - Sijie
>

Re: [DISCUSSION] Podling name search

2018-06-07 Thread Jia Zhai 
+1 for continuing to use the name “Apache Pulsar”.



On Fri, Jun 8, 2018 at 8:03 AM, Sanjeev Kulkarni 
wrote:

> +1 for continuing to use the name “Apache Pulsar”.
>
> On Thu, Jun 7, 2018 at 5:01 PM Matteo Merli  wrote:
>
> > As some in Pulsar community are already aware, one of the pending
> > tasks for Pulsar project to complete the "name search task".
> >
> > A JIRA task was opened to collect facts around usages of Pulsar
> > name: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-141
> >
> > I had forwarded that to trademarks@ and this was the response
> > from Mark Thomas.
> >
> > > Pulsar is a very popular name for software.
> > >
> > > I don't see any obvious conflicts but given the popularity of the name
> > > it is likely, in a global marketplace, that there will be some.
> > >
> > > Should the project wish to register the "PULSAR" mark in the future, it
> > > is uncertain whether the ASF would be able to. Registering "APACHE
> > > PULSAR" is unlikely to hit any difficulties.
> > >
> > > It is more likely than usual that an infringement will emerge in the
> > > future that would require the project to rename.
> > >
> > > The podling needs to make a choice. Either:
> > >
> > > a) continue using PULSAR and accept that:
> > >- there are likely to be some restrictions on how the name is used
> > >  (primarily that it always has to be APACHE PULSAR)
> > >- it is more likely than for most ASF projects that the project
> > >  will be required to rename due to an infringement
> > >
> > > or
> > >
> > > b) pick a new name
> > >
> > > No rush on this. The podling should take time to discuss this.
> >
> >
> > Therefore we need to take a decision on this matter.
> >
> > My personal inclination is to continue to use "Apache Pulsar" and
> > have that to be registered as a trademark of ASF.
> >
> > My reasoning:
> >
> >  * We are anyway already always referring to "Apache Pulsar"
> >rather than just "Pulsar"
> >
> >  * Changing name at this point in life of the project would be
> >very disruptive. We just spent the past year into building
> >some naming awareness and it would all vanish, not to mention
> >the huge amount of work in updating documentation, package
> >names, etc.
> >
> >  * If a conflict arise later on, it might be easier to change
> >name at that point. Once the project has a larger community
> >and bigger recognition, changing name would not mean to
> >restart from scratch.
> >
> >
> > I propose to have anyone share they thoughs on this issue. Once
> > there is a prevalent inclination in the community, we can vote a
> > final resolution on the subject.
> >
> > Thanks,
> > Matteo
> >
> >
> >
> > --
> > Matteo Merli
> > 
> >
>

Re: [DRAFT] Pulsar Podling report June 2018

2018-06-06 Thread Jia Zhai 
+1, exciting to see we are nearing graduation!

On Thu, Jun 7, 2018 at 9:53 AM, Sijie Guo  wrote:

> +1 this is a great milestone. exciting to see we are nearing graduation!
>
> - Sijie
>
> On Wed, Jun 6, 2018 at 8:57 AM, Matteo Merli  wrote:
>
> > Here is the draft for the podling report. Please submit feedback soon,
> the
> > deadline is today (sorry for sending draft at last moment).
> >
> >
> > 
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub semantics over topics,
> > guaranteed at-least-once delivery of messages, automatic cursor
> management
> > for
> > subscribers, and cross-datacenter replication.
> >
> > Pulsar has been incubating since 2017-06-01.
> >
> > Most important issues to address in the move towards graduation:
> >
> >   1. Complete the Podling name search tasks. The task is in progress
> right
> > now.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> > of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >
> >   The community added 7 new contributors that submitted pull-requests
> which
> >   were merged into master.
> >
> >   The number of users approaching the team on the Slack channel has kept
> >   steadily increasing since the last report. Many users have actively
> > deployed
> >   Pulsar for evaluation and production use cases.
> >
> >   Project members from several companies have organized or participated
> in
> >   several meetups, presenting Pulsar's introductions, deep-dives and
> > hands-on
> >   tutorial, including recorded podcasts. We have several scheduled talks
> on
> >   Pulsar at various conferences, 2 at ApacheCon in September, one at
> OSCon
> > in
> >   July and 2 others at Strata New York in September. A Pulsar dedicated
> > meetup
> >   is being organized for next July.
> >
> >   Since the last report the number of weekly-active-users on the Slack
> > channel
> >   has increased from 53 to 88.
> >
> >   We have reached the 1 year mark since Pulsar entering the Apache
> > Incubator.
> >   Here is a summary of the community developments over the past year:
> >
> >
> >   1. Pulsar community has done 5 Apache releases since entering
> >  incubator. The release process is well documented and we have
> >  had 4 different release managers from 3 different companies.
> >
> >   2. We have added 3 committers and PPMC members since incubation and
> >  there are also other candidates who have already made significant
> >  contributions to the project.
> >
> >   3. Community of users and people interested in Pulsar has expanded
> >  considerably. Thanks to the months long work in improving ease of
> >  use, documentation and blogs, many people became aware of Pulsar
> >  and started playing with it, then evaluating it and finally
> >  putting it in production for critical use cases.
> >
> >   4. We have tried to help users getting started through any
> >  communication channel. Even though we keep trying to encourage
> >  people to use the mailing list, most of the first interactions
> >  have been happening through the Slack channel. We also did make
> >  sure that:
> >
> >  a) No decisions are taken in Slack channel
> >
> >  b) Developers technical discussion happen mostly in Github
> > issue/Pull-Request or in developers mailing list
> >
> >  c) Conversations in Slack are sent to dev/user mailing list in a
> > daily digest form for archival and to be searchable
> >
> >  In any case Slack has been working fairly well in engaging with
> >  users, by providing a tool to have very quick informal
> >  question/answer interactions that were very appreciated by users.
> >
> >5. Overall, there were a lot of healthy discussions, with feedback
> >   and collaborations from people from different companies and
> >   different perspectives that resulted in much stronger design
> >   decisions and ultimately a better system.
> >
> >6. We have taken several steps to increase awareness, like blog
> >   posts, meetups (both dedicated to Pulsar or dedicated to similar
> >   topics) and presentations to conferences, like Strata or
> >   ApacheCon (where we have 2 talks scheduled for next September).
> >
> > How has the project developed since the last report?
> >
> >   23 authors have pushed 469 commits to master in the last 3 months.
> >
> >   The project has made the its fifth release since joining the
> >   Apache Incubator (2.0.0-rc1-incubating on May 29th). This was a
> >   major release that culminated several months of works and lays the
> >   foundation for the next stage in Pulsar development. New major
> >   features include:
> >* Pulsar Functions (Lightweight compute framework)
> >* Schema registry
> >* Topic compaction
> >
> >   Community is actively working on next milestone, 2.1 release

Re: Planning for patch release 2.0.1

2018-06-04 Thread Jia Zhai 


On Sat, Jun 2, 2018 at 5:13 AM, Matteo Merli  wrote:

> Since we have released 2.0.0-rc1-incubating, a few issues were reported
> from users.
>
> Most of them are already being fixed. The list of fixes and PRs is at
> https://github.com/apache/incubator-pulsar/milestone/14
>
> My intention would be to have a quick patch release that addresses all
> these issues in 2.0 and start the release process by next Monday, since few
> issues in packaging are preventing some features to work properly (proxy,
> Python client).
>
> Any thoughts? Any other changes that anyone feel should go in the patch
> release?
>
> Matteo
> --
> Matteo Merli
> 
>

[ANNOUNCE] 2 Apache Pulsar talks at June 25--26 in LC3, Beijing China

2018-06-04 Thread Jia Zhai 
Hi all,

There will be 2 Apache Pulsar talks at "LinuxCon + ContainerCon +
CloudOpen2018, June 25--26, Beijing, China":
1:  How a Segment-oriented Architecture Delivers Better Performance

In this talk, Jia will discuss how this layered architecture allows Pulsar
to achieve a high level of scalability and performance.


The time of it will be:
"Monday, June 25 • 15:00 - 15:40"
And here is the link, which contains more information:
https://lc32018.sched.com/event/ERAn/how-a-segment-oriented-architecture-delivers-better-performance-jia-zhai-streamlio


2:  Light Weight Computing for IOT/Edge Using Pulsar Functions
In this talk, Sijie/Jia will talk about Apache Pulsar Functions in IOT/Edge
Computing area.


The time of it will be:
"Tuesday, June 26 • 16:20 - 17:00"
And here is the link, which contains more information:
https://lc32018.sched.com/event/ERAI/light-weight-computing-for-iotedge-using-pulsar-functions-sijie-guo-streamlio

Best Regards.
-Jia

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5

2018-05-23 Thread Jia Zhai 
+1 (non-binding)

Environment: macOS 10.13.2

* asc, sha1, sha512 are good for both src and binary distributions
* binary distribution
   - run standalone
   - be able to produce and consume messages
* src distribution
   - passed compile and all unit test.
   - run standalone with compiled binary, be able to produce and consume.


On Wed, May 23, 2018 at 2:28 AM, Dave Fisher  wrote:

> Hi -
>
> +1 (binding)
>
> $ mvn --version
> *Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T12:39:06-07:00)*
> Maven home: /Users/davewave/Development/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_
> 131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>
> Checksums for bin and src both sha1 and sha512 are correct.
> Signature for both bin and src is Matteo.
> License, Notice, and Disclaimer files are present and look good. I’m ok
> with references into a licenses directory for the convenience binary.
> Built src following instructions in README.md.
> Please note that
> $ bin/pulsar standalone
> Fails if the base pulsar directory has been renamed after the build. The
> error is:
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/pulsar/client/admin/PulsarAdminException
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> at java.lang.Class.getMethod0(Class.java:3018)
> at java.lang.Class.getMethod(Class.java:1784)
> at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544)
> at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526)
> Caused by: java.lang.ClassNotFoundException: org.apache.pulsar.client.
> admin.PulsarAdminException
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 7 more
> A quick scan of the commands did not reveal the trouble - the scripting
> looks good to me.
>
> Regards,
> Dave
>
> On May 20, 2018, at 6:23 PM, Matteo Merli  wrote:
>
> This is the fifth release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
>
> The only difference from previous candidate is a fix on the LICENSE
> attached
> to bin distribution to correctly reflect all dependencies and versions.
>
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/12?closed=1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-2.0.0-rc1-incubating-candidate-5/
>
> SHA-1 checksums:
> 72ee624c9b1485cc4c12b71e3807c7c05ec900ad
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> c525457db8f9c4ea859c595c93e9207631cda19f
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1017/
>
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-5 (08708a198606fb934e46f6cb0b614f
> 2babf613e4)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.0-rc1-incubating-candidate-5
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> --
> Matteo Merli
> 
>
>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

2018-05-15 Thread Jia Zhai 
+1 (non-binding)

Environment: macOS 10.13.2

* asc, sha1, sha512 are good for both src and binary distributions
* binary distribution
   - run standalone
   - be able to produce and consume messages
* src distribution
   - passed compile and all unit test.
   - run standalone with compiled binary, be able to produce and consume.

On Wed, May 16, 2018 at 9:40 AM, Rajan Dhabalia 
wrote:

> +1 (binding)
>
> Environment: Mac-OS 10.12.6
>
> Checked:
>  - signatures and checksum
>  - maven repository artifacts
>  - start standalone service and client-test for producer/consumer (src/bin
> distribution)
>  - rat check on src distribution
>  - compile and unit test on src distribution
>
> Thanks,
> Rajan
>
> On Mon, May 14, 2018 at 4:33 PM, Matteo Merli  wrote:
>
> > This is the fourth release candidate for Apache Pulsar, version
> > 2.0.0-rc1-incubating.
> >
> > It fixes the following issues:
> > https://github.com/apache/incubator-pulsar/milestone/12?closed=1
> >
> > *** Please download, test and vote on this release. This vote will stay
> > open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > pulsar-2.0.0-rc1-incubating-candidate-4/
> >
> > SHA-1 checksums:
> > a959a33500508d0ba690ca177eb39cf83dddf022
> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b
> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1014/
> >
> > The tag to be voted upon:
> > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f
> > 5eb4118de7)
> > https://github.com/apache/incubator-pulsar/releases/tag/
> > v2.0.0-rc1-incubating-candidate-4
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> >
> > Please download the the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> > --
> > Matteo Merli
> > 
> >
>

Re: Planning for Pulsar 2.1 release

2018-05-13 Thread Jia Zhai 
 

On Fri, May 11, 2018 at 1:51 AM, Sanjeev Kulkarni 
wrote:

> Looks good!
>
> On Thu, May 10, 2018 at 9:12 AM, Matteo Merli  wrote:
>
> > Now that 2.0 is on the way, I'd like to get some items that we're
> targeting
> > to get into a 2.1 release:
> >
> >  * Connector framework (pulsar-io), built on top of Pulsar Functions
> >  * Go client library (based on C++ Pulsar client lib)
> >  * Tooling and docs around rack-aware deployment
> >  * Tiered storage framework (with S3 as first supported backend)
> >  * Schema integration for unctions
> >  * Distributed state in functions
> >  * Avro schema support
> >  * Improvements in pulsar-admin cli tool
> >
> > The idea would be to have a 2.1 release in early June.
> >
> > What are the thoughts around this?
> >
> > Matteo
> > --
> > Matteo Merli
> > 
> >
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

2018-05-09 Thread Jia Zhai 
+1 (non-binding)

Environment: macOS 10.13.2

* asc, sha1, sha512 are good for both src and binary distributions
* binary distribution
   - run standalone
   - be able to produce and consume messages
* src distribution
   - passed compile and all unit test.
   - run standalone with compiled binary, be able to produce and consume.



On Wed, May 9, 2018 at 9:11 AM, Sijie Guo  wrote:

> +1 (binding)
>
> Environment: macOS 10.13.1
>
> * asc, sha1, sha512 are good for both src and binary distributions
> * binary distribution
>- run standalone
>- be able to produce and consume messages
>- run perf
>- run functions
> * src distribution
>- be able to compile and run same set of tests on compiled binary
> * rat check is good
>
> - Sijie
>
> On Wed, May 9, 2018 at 6:22 AM, Matteo Merli  wrote:
>
> > This is the third release candidate for Apache Pulsar, version
> > 2.0.0-rc1-incubating.
> >
> > It fixes the following issues:
> > https://github.com/apache/incubator-pulsar/milestone/12?closed=1
> >
> > *** Please download, test and vote on this release. This vote will stay
> > open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > pulsar-2.0.0-rc1-incubating-candidate-3/
> >
> > SHA-1 checksums:
> > b1a392c5935448da195eb927520fe6deb20182fc
> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> > 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> >
> > The tag to be voted upon:
> > v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16
> > fc702404ef)
> > https://github.com/apache/incubator-pulsar/releases/tag/
> > v2.0.0-rc1-incubating-candidate-3
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> >
> > Please download the the source package, and follow the README to build
> > and run the Pulsar standalone service.
> > --
> > Matteo Merli
> > 
> >
>

Re: [ANNOUNCE] Apache BookKeeper 4.7.0 released

2018-04-20 Thread Jia Zhai 
con~

On Fri, Apr 20, 2018 at 4:34 PM, Sijie Guo  wrote:

> The Apache BookKeeper team is proud to announce Apache BookKeeper version
> 4.7.0.
>
> 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 10th release of Apache BookKeeper.
>
> This is a feature release. It is a great milestone for Apache BookKeeper.
> We finally merge changes from both Salesforce and Yahoo branches to
> upstream. Apache Pulsar also switched to use official 4.7.0 release for its
> upcoming 2.0 release.  It is also the first release of Apache
> DistributedLog after it is merged as sub modules of Apache BookKeeper.
>
> This release adopts 7 BPs and fixes 446 issues. It introduces new metadata
> service API, rocksdb based ledger storage, have extensive performance
> enhancements around reducing jvm garbage collection, reducing lock
> contentions, and various improvements around operability.
>
> For BookKeeper release details and downloads, visit:
>
> https://bookkeeper.apache.org/releases/
>
> BookKeeper 4.7.0 Release Notes are at:
>
> http://bookkeeper.apache.org/docs/4.7.0/overview/releaseNotes/
>
> We would like to thank all the contributors that made the release possible.
>
> Regards,
>
> The BookKeeper Team
>

Re: minor/bugfix release

2018-04-20 Thread Jia Zhai 
+1

On Fri, Apr 20, 2018 at 2:19 PM, Sijie Guo  wrote:

> Thank you Jai!
>
> - Sijie
>
> On Thu, Apr 19, 2018 at 11:42 AM, Jai Asher  wrote:
>
> > +1 to 1.22.1 release - I think a bug fix (patch) release is a great idea
> > especially if we have user-facing bugs. Since I was responsible for
> > releasing 1.22, I don't mind taking up this task.
> >
> >
> > On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo  wrote:
> >
> > > Hi all,
> > >
> > > I think there are a couple of bugs reported on 1.22.0 when users are
> > using
> > > it. Shall we consider doing a 1.22.1 release?
> > >
> > > - Sijie
> > >
> > > On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:
> > >
> > > > Hi all,
> > > >
> > > > Currently pulsar release schedule is mainly on feature releases. Any
> > idea
> > > > on bugfix releases?
> > > >
> > > > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
> > > > release with bug fixes?
> > > >
> > > > Thoughts?
> > > >
> > > > - Sijie
> > > >
> > > >
> > >
> >
>

Re: Plan for Pulsar 2.0 release

2018-04-18 Thread Jia Zhai 
+1

On Tue, Apr 17, 2018 at 2:25 PM, Jai Asher  wrote:

> +1 for releasing the RC early
>
> On Mon, Apr 16, 2018 at 6:52 PM Sijie Guo  wrote:
>
> > +1 for releasing an RC version prior to an official release.
> >
> > On Fri, Apr 13, 2018 at 9:27 AM, Matteo Merli  wrote:
> >
> > > Hi everyone,
> > >
> > > I think we are approaching the completion of most major items that were
> > > scheduled for 2.0 release.
> > >
> > > Since there is a big number of items that went in, like for example:
> > >  * Migrating BookKeeper from Yahoo branch based on 4.3 to main Apache
> 4.7
> > >  * Schema
> > >  * Topic Compaction
> > >  * Functions
> > >  * Client API refactorings
> > >
> > > I would suggest to have a "2.0.0-RC1" release, still officially
> released
> > > with regular process, so that we'll have a chance to iron out any bugs,
> > > tools or packaging issue before marking 2.0 as "stable".
> > >
> > > My idea is use next week to finish up all the pending tasks and
> > > documentation changes and kickoff the release process for 2.0.0-rc1 in
> > the
> > > week after.
> > >
> > > Any thoughts with respect to this?
> > >
> > > Matteo
> > > --
> > > Matteo Merli
> > > 
> > >
> >
>

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

2018-02-23 Thread Jia Zhai 
+1 (non-binding)

Environment: MacOS 10.13

* Bin distribution
-checked md5, sha, asc,
-start standalone,
-producer/consumer worked,
* Src distribution
-checked md5, sha, asc,
-compile and unit tests,
-start standalone,
-producer/consumer worked




On Fri, Feb 23, 2018 at 4:02 PM, Masahiro Sakamoto 
wrote:

> +1 (binding)
>
> Environment: CentOS 6.7
>
> * checked md5, sha, asc
> * ran standalone
> * producer/consumer worked normally
> * compiling and unit tests succeeded
> * rat check
>
> - Masahiro
>
> --
> Masahiro Sakamoto
> Yahoo Japan Corp.
> E-mail: massa...@yahoo-corp.jp
> --
>
> > -Original Message-
> > From: Jai Asher [mailto:jai.ashe...@gmail.com]
> > Sent: Wednesday, February 21, 2018 1:39 PM
> > To: dev@pulsar.incubator.apache.org
> > Subject: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3
> >
> > This is the fourth release candidate for Apache Pulsar, version
> > 1.22.0-incubating.
> >
> > It fixes the following issues:
> > https://github.com/apache/incubator-pulsar/milestone/11?closed=1
> >
> > *** Please download, test and vote by Friday, Feb 23, 2018, 10:00 GMT.
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-1.22.0-
> > incubating-candidate-3/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-101
> > 0/
> >
> > The tag to be voted upon:
> > v1.22.0-incubating-candidate-3
> > (5d14788e510faec23fd8ed189ed343e93b489dda)
> > https://github.com/apache/incubator-pulsar/releases/tag/v1.22.0-incuba
> > ting-candidate-3
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> >
> > Please download the source package, and follow the README to build and
> run
> > the Pulsar standalone service.
>

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

2017-12-09 Thread Jia Zhai 
+1 (non-binding)

Environment: MacOS 10.13.1

Checked:
 * CRCs: md5, sha1, and asc.
 * Bin distribution:
 - Start standalone service and producer/consumer test
 * Src distribution:
 - Compile and unit tests
 - RAT check
 - Start standalone service


On Sat, Dec 9, 2017 at 9:35 AM, Matteo Merli  wrote:

> +1 (binding)
>
> Environment: MacOS 10.12 & Centos-7.4
>
> Checked:
>  * Signatures, crc
>  * Bin distribution:
>  - NOTICE, README, LICENSE
>  - Start standalone service and producer/consumer test
>  * Src distribution:
>  - NOTICE,  README, LICENSE
>  - Compile and unit tests
>  - RAT check
>  - Start standalone service
>  * Checked staging maven repository artifacts
>
>
> Matteo
>
>
> On Wed, Dec 6, 2017 at 3:35 AM Nozomi Kurihara 
> wrote:
>
> > This is the FOURTH release candidate for Apache Pulsar, version
> > 1.21.0-incubating.
> >
> > It fixes the following issues:
> > https://github.com/apache/incubator-pulsar/milestone/10?closed=1
> >
> >
> > *** Please download, test and vote by December 11th 2017, 12:00 GMT.
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-1.21.0-incubating-candidate-3/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1005/
> >
> > The tag to be voted upon:
> > v1.21.0-incubating-candidate-3
> >
> >
> > https://github.com/apache/incubator-pulsar/releases/tag/
> v1.21.0-incubating-candidate-3
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> >
> > Please download the the source package, and follow the README to build
> and
> > run the Pulsar standalone service.
> >
> > Thanks,
> > Nozomi
> >
> --
> Matteo Merli
> 
>

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 2

2017-12-01 Thread Jia Zhai 
+1,

Environment: MacOS 10.13.1

Checked:
 * CRCs: md5 and sha1,
 * Bin distribution:
 - Start standalone service and producer/consumer test
 * Src distribution:
 - Compile and unit tests
 - RAT check
 - Start standalone service

PS, RAT check passed on my check.

But some 2 small issues that I met:
1,  seems gpg signature need signed by others.

```
gpg --verify apache-pulsar-1.21.0-incubating-bin.tar.gz.asc
apache-pulsar-1.21.0-incubating-bin.tar.gz


gpg: Signature made Thu Nov 30 13:25:16 2017 CST

gpg:using RSA key 000A0885253005EBF749E283A92D27AAC3D80414

gpg: Good signature from "Nozomi Kurihara (CODE SIGNING KEY) <
nkuri...@apache.org>" [unknown]

gpg: WARNING: This key is not certified with a trusted signature!

gpg:  There is no indication that the signature belongs to the
owner.

Primary key fingerprint: 000A 0885 2530 05EB F749  E283 A92D 27AA C3D8 0414
```

2,  some findbugs error reporting for src, by command "mvn findbugs:check ":

```

[INFO] com.scurrilous.circe.HashSupport$SetComparator implements Comparator
but not Serializable [com.scurrilous.circe.HashSupport$SetComparator] At
HashSupport.java:[lines 173-176] SE_COMPARATOR_SHOULD_BE_SERIALIZABLE

[INFO] com.scurrilous.circe.params.SimpleHashParameters.equals(Object)
fails for subtypes [com.scurrilous.circe.params.SimpleHashParameters] At
SimpleHashParameters.java:[line 51] EQ_GETCLASS_AND_CLASS_CONSTANT

[INFO]
org.apache.pulsar.checksum.utils.NativeUtils.loadLibraryFromJar(String) may
fail to clean up java.io.InputStream on checked exception
[org.apache.pulsar.checksum.utils.NativeUtils,
org.apache.pulsar.checksum.utils.NativeUtils,
org.apache.pulsar.checksum.utils.NativeUtils] Obligation to clean up
resource created at NativeUtils.java:[line 62] is not dischargedPath
continues at NativeUtils.java:[line 63]Path continues at
NativeUtils.java:[line 67] OBL_UNSATISFIED_OBLIGATION_EXCEPTION_EDGE

[INFO] Exceptional return value of java.io.File.delete() ignored in
org.apache.pulsar.checksum.utils.NativeUtils.loadLibraryFromJar(String)
[org.apache.pulsar.checksum.utils.NativeUtils] At NativeUtils.java:[line
51] RV_RETURN_VALUE_IGNORED_BAD_PRACTICE

[INFO]

```

On Fri, Dec 1, 2017 at 10:29 AM, Nozomi Kurihara 
wrote:

> Hi Dave,
>
>
> Thanks for your detailed check.
>
>
> However, I have not seen
>
>
> > - rat check.
>
> > Files missing headers: dependency-reduced-pom.xml which is generated.
> > Please add an exclude to the pom.xml:
> > 720d719
> > < **/dependency-reduced-pom.xml
>
> by executing $mvn apache-rat:check in the src package.
> Could you tell me the reproducing procedure?
>
> Thanks,
> Nozomi
>
> 
> 差出人: Dave Fisher 
> 送信日時: 2017年12月1日 8:37:50
> 宛先: dev@pulsar.incubator.apache.org
> 件名: Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 2
>
> +1 (IPMC Binding)
>
> Environment: macOS 10.12.6
>
> Checked all signatures and check sums - SHA is 512 bits.
>
> BIN distribution.
> - NOTICE, README, LICENSE and DISCLAIMER.
> ——> Binary licenses are in a subdirectory and probably ought to be in the
> full LICENSE file. For next time IMHO.
> - Started the standalone service - I’m not sure how well it worked, but
> had a lot of INFO log messages.
>
> SRC distribution
> - NOTICE. README, LICENSE and DISCLAIMER
> - mvn install - all tests passed.
> - rat check.
> Files missing headers: dependency-reduced-pom.xml which is generated.
> Please add an exclude to the pom.xml:
> 720d719
> < **/dependency-reduced-pom.xml
>
> - Started the standalone service - looked similar to the bin results.
>
> It is up to the Release Manager to decide to fix the exclude now and recut
> the release or wait until next release.
> I also recommend removing the inactive license check plugin -
> license-maven-plugin
>
> Regards,
> Dave
>
> On Nov 30, 2017, at 10:00 AM, Matteo Merli > wrote:
>
> +1 (binding)
>
> Environment: MacOS 10.12
>
> Checked:
> * Signatures, crc
> * Bin distribution:
> - NOTICE, README, LICENSE
> - Start standalone service and producer/consumer test
> * Src distribution:
> - NOTICE,  README, LICENSE
> - Compile and unit tests
> - RAT check
> - Start standalone service
> * Checked staging maven repository artifacts
>
> Matteo
>
>
> On Wed, Nov 29, 2017 at 9:57 PM Nozomi Kurihara  mailto:nkuri...@yahoo-corp.jp>>
> wrote:
>
> This is the THIRD release candidate for Apache Pulsar, version
> 1.21.0-incubating.
>
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/10?closed=1
>
> *** Please download, test and vote by December 5th 2017, 10:00 GMT.
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
>
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-1.21.0-incubating-candidate-2/
>
> Maven staging repo:
>

Re: [VOTE] Pulsar 1.19.0-incubating Release Candidate 0

2017-08-02 Thread Jia Zhai 
+1 (non-binding)
- verified the packages (md5, sha1 and signature)
- Checked the build success
- Run the binaries by 'bin/pulsar standalone'

On Thu, Aug 3, 2017 at 8:57 AM, Nozomi Kurihara 
wrote:

> +1
>
> - Confirmed md5
> - Checked the build success
> - Ran the binaries
>
> Thanks!
>
> Nozomi
>
> 2017/08/03 9:32 に、"Sijie Guo"  を書き込みました:
>
> +1 (non-binding)
>
> - verified the packages (md5, sha1 and signature)
> - maven artifacts looks good to me.
> - successfully build the source package
> - run the binary package following the instructions in the website
>
> - Sijie
>
> On Wed, Aug 2, 2017 at 3:07 PM, Rajan Dhabalia 
> wrote:
>
> > +1. I ran the regression-tests and few of the load-tests with this
> version
> > and looks fine.
> >
> > Thanks,
> > Rajan
> >
> > On Wed, Aug 2, 2017 at 1:36 PM, Dave Fisher 
> wrote:
> >
> > > Hi -
> > >
> > > I will cast an IPMC vote.
> > >
> > > +1 Release!
> > >
> > > I checked the source and binary package hashes.
> > > I built the project with Maven from the source package.
> > > I ran the rat check and checked the rat report.
> > > Discussed the Category B issues which look good for now.
> > >
> > > Regards,
> > > Dave
> > >
> > > > On Aug 2, 2017, at 12:47 PM, Matteo Merli 
> wrote:
> > > >
> > > > Remainder for all committers:
> > > >
> > > > please check the release artifacts and vote on this thread,
> before
> > > tomorrow
> > > > 3pm PDT.
> > > >
> > > > Vote as in :
> > > >
> > > > [ ] +1 Release this package
> > > > [ ] 0 I don't feel strongly about it, but don't object
> > > > [ ] -1 Do not release this package because...
> > > >
> > > >
> > > > The documentation on the release process and what needs to be
> included
> > > can
> > > > be found at:
> > > >   - https://incubator.apache.org/guides/releasemanagement.html
> > > >   - http://www.apache.org/legal/release-policy.html
> > > >   - http://www.apache.org/dev/release-distribution.html
> > > >   - http://www.apache.org/dev/release-publishing.html
> > > >   - http://www.apache.org/dev/publishing-maven-artifacts.html
> > > >
> > > > --
> > > > Matteo Merli
> > > > 
> > > >
> > > > On Mon, Jul 31, 2017 at 2:39 PM, Matteo Merli  >
> > wrote:
> > > >
> > > >> This is the first release candidate for Apache Pulsar, version
> > > >> 1.19.0-incubating.
> > > >>
> > > >> Major changes included in this release are:
> > > >> * Added stateless Pulsar proxy
> > > >> * Support for non-persistent topics
> > > >> * Upgraded RocksDB to comply with ASF policy
> > > >> * Instrumentation of ZooKeeper client to expose metrics
> > > >> * Fixes for TLS auth in WebSocket proxy
> > > >>
> > > >>
> > > >> Complete list of changes can be found at:
> > > >>
> > > >> https://github.com/apache/incubator-pulsar/milestone/8?closed=1
> > > >>
> > > >> *** Please download, test and vote by August 3th 2017, 15:00
> PDT.
> > > >>
> > > >> Note that we are voting upon the source (tag), binaries are
> provided
> > for
> > > >> convenience.
> > > >>
> > > >> Source and binary files:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > > >> pulsar-1.19.0-incubating-candidate-0/
> > > >>
> > > >> Maven staging repo:
> > > >> https://repository.apache.org/content/repositories/
> > > orgapachepulsar-1000/
> > > >>
> > > >> The tag to be voted upon:
> > > >> v1.19.0-incubating-candidate-0 (5125279b50f7a3da8c211b698580e1
> > > d2f4dd65e2)
> > > >>
> > > >> Pulsar's KEYS file containing PGP keys we use to sign the
> release:
> > > >> https://dist.apache.org/repos/dist/release/incubator/pulsar/
> KEYS
> > > >>
> > > >> Please download the the source package, and follow the README
> to build
> > > >> and run the Pulsar standalone service.
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Matteo Merli
> > > >> 
> > > >>
> > >
> > >
> >
>
>
>