Re: Pulsar release 2.2

+1 sgtm On Mon, Sep 17, 2018 at 11:30 AM Joe F wrote: > Now that 2.1.1 is completed, I intend to start the Pulsar 2.2 release > process in a few days, and would like to freeze the code this Friday. > > Please ensure that all your committed PR's are merged and complete. I still > see 11

Re: Planning for Pulsar 2.2 release

release. Once all the issues are merged, we should start the process for releasing 2.2 https://github.com/apache/incubator-pulsar/milestone/16 Thanks, Sijie On Mon, Aug 20, 2018 at 2:58 PM Sijie Guo wrote: > Thank you Joe! :) > > - Sijie > > On Mon, Aug 20, 2018 at 2:51 PM Joe F

Re: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1

+1 Environment: MacOS 10.13.1 - All asc, sha512 files are good. (sha1 files can be dropped, but minor issues) - binary is good, verified pub/sub, functions and connectors - src is good, can compile, rat check, and can run pub/sub, functions and connectors after compilation. - Sijie On Thu, Sep

Re: [VOTE] Graduation resolution proposal

ia Zhai > * Jim Jagielski > * Joe Francis > * Ludwig Pummer > * Masahiro Sakamoto > * Masakazu Kitajo > * Matteo Merli > * Nozomi Kurihara > * P. Taylor Goetz > *

Re: [DRAFT] [UPDATED] Graduation resolution proposal

gt; > > >> subscribers, and cross-datacenter replication; and be it > further > > > > >> > > > > >> RESOLVED, that the office of "Vice President, Apache Pulsar" > be > > > and > > > > >

Re: [DRAFT] Podling report

+1 looks good - Sijie On Wed, Sep 5, 2018 at 5:36 PM Matteo Merli wrote: > Sorry for sending out at very last minute (deadline is today). Please take > a look. > > I have added a paragraph regarding the branding discussion that happen in > early June (as discussed with Taylor then) since the

Re: [discuss] how to label milestone

on merging a PR. here is the script: https://github.com/apache/incubator-pulsar/pull/2526 This is one example PR how it was merged by the script: https://github.com/sijie/incubator-pulsar/pull/8 Let me know what do you think. - Sijie On Mon, Aug 27, 2018 at 2:45 AM Sijie Guo wrote: > Hi

Re: [discuss] how to label milestone

On Mon, Sep 3, 2018 at 12:14 AM Ivan Kelly wrote: > > All the bug fixes are deferred to release manager cherry-picking to bug > fix > > branches. Since master and branches are quickly diverged with changes, > > it is very painful for cherry-picks later and there is no clear process > for > >

[ANNOUNCE] Apache BookKeeper 4.7.2 released

The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.7.2. 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

Re: Podling Report Reminder - September 2018

We have a podling report due this wednesday. Anyone volunteers in drafting the report? - Sijie On Sun, Sep 2, 2018 at 5:55 PM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to >

Re: [DRAFT] Graduation resolution proposal

t; * Ivan Brendan Kelly > * Jai Asher > * Jia Zhai > * Jim Jagielski > * Joe Francis > * Ludwig Pummer > * Masahiro Sakamoto > * Masakazu Kitajo > * Matteo Merli > * Nozomi Kurihar

Re: [DISCUSSION] Pulsar maturity model assessment

Great work, Matteo! +1; #shipit - Sijie On Mon, Aug 27, 2018 at 11:43 PM Matteo Merli wrote: > I have started a draft of the maturity model assessment. > > You can find it on the wiki: > > https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar > > Please

Re: PIP 23 : Message Tracing By Interceptors

On Fri, Aug 24, 2018 at 6:04 PM Matteo Merli wrote: > > Original, i just want to implement tracing by interceptors. We don’t must > > to binding “tracing” and “interceptors” together. > > I thougt that to implement message tracing in pulsar, we should implement > > interceptors before. And

Re: PIP 23 : Message Tracing By Interceptors

proposed #intercept(...)? I am not sure we need to distinguish "tracing" from other interceptors. client.newConsumer() .topic("xyz") .subscriptionName("yyz") .intercept(OpenTracingInterceptor.of(tracingLoggerConfig)) > .subscribe();

Re: Starting the Graduation Process

On Thu, Aug 23, 2018 at 5:17 PM Dave Fisher wrote: > Hi - > > I think that the Pulsar community is just about ready to graduate to a Top > Level Project. > > The graduation guide is here. [1] > The incubation status file is here. [2] I made some changes today which > have yet to propagate. They

Re: PIP 23 : Message Tracing By Interceptors

Updated. Thanks, Penghui! - Sijie On Tue, Aug 21, 2018 at 3:56 AM 李鹏辉 wrote: > Please add zhaijia to Authors. > > Sijie Guo 于2018年8月21日周二 下午6:48写道： > > > Thank you penghui! This is a great feature to add to Pulsar. > > > > I've copied your PIP to pulsar

Re: PIP 23 : Message Tracing By Interceptors

Thank you penghui! This is a great feature to add to Pulsar. I've copied your PIP to pulsar wiki as well : https://github.com/apache/incubator-pulsar/wiki/PIP-23:-Message-Tracing-By-Interceptors - Sijie On Tue, Aug 21, 2018 at 3:14 AM 李鹏辉 wrote: > Dear all > > This is a PIP to add feature of

Re: Planning for Pulsar 2.2 release

Thank you Joe! :) - Sijie On Mon, Aug 20, 2018 at 2:51 PM Joe F wrote: > Ok if no one else is there i will take this > > Joe > > On Mon, Aug 20, 2018, 2:45 PM Sijie Guo wrote: > > > Anyone volunteer for releasing 2.2? > > > > - Sijie > > > > O

Re: Planning for Pulsar 2.2 release

t 2:45 PM Sijie Guo wrote: > > > Anyone volunteer for releasing 2.2? > > > > - Sijie > > > > On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo wrote: > > > > > Any committer volunteer for releasing 2.2? > > > > > >

Re: Planning for Pulsar 2.2 release

Anyone volunteer for releasing 2.2? - Sijie On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo wrote: > Any committer volunteer for releasing 2.2? > > - Sijie > > On Wed, Aug 8, 2018 at 11:43 AM Sanjeev Kulkarni > wrote: > >> The timeline sounds good! >> One more

Re: PIP 20: Mechanism to revoke TLS authentication

On Mon, Aug 20, 2018 at 5:59 AM Ivan Kelly wrote: > > Instead of using zookeeper, can we consider using a managed ledger or a > system topic for keeping all these revoked keys? > > Do we already have an example of a system topic in use? Functions is using system topics. And all its topics are

Re: Planning for Pulsar 2.2 release

is > task as well. > > > On Wed, Aug 8, 2018 at 11:40 AM Sijie Guo wrote: > > > Hi all, > > > > Although we just announced 2.1, we already have a lot of new features > > merged since 2.1 candidate is cut. For example, Pulsar SQL, GCS support > as > >

[DISCUSS] Pulsar 2.1.1 Release

Hi all, It has been 2 weeks since 2.1.0 released. There were bunch of issues reported by users and fixes have been merged. I am thinking of starting a 2.1.1 release next week. Any thoughts? - Sijie

Re: PIP 20: Mechanism to revoke TLS authentication

Ivan, Thank you for writing this up. This PIP looks great to me! +1 just one question: > This will add the subject key identifier to zookeeper under /tls/revoked/. All brokers and proxies cache the children /tls/revoked. Instead of using zookeeper, can we consider using a managed ledger or a

Re: PIP 22 : Pulsar Dead Letter Topic

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

Pulsar Blog

FYI. Now we have a blog entry in apache website: https://pulsar.incubator.apache.org/blog/ for latests updates of Apache Pulsar. This is the RSS feed : https://pulsar.incubator.apache.org/blog/feed.xml - Sijie

Re: Consult: PIP work progress

Zongyang, Thank you for reaching out to Pulsar community. In general, PIP is used for proposing new features, improvements and user impact changes. However I don't think Pulsar community has defined any strict rules for people submitting PIP. The general rule for PIP is for people in the

[discuss] how to label milestone

Hi all, It seems we don't have a standard for labelling milestone. sometimes I am not lost and confused when I see a change was merged to master but marked in a bug fix milestone. so I am raising a discussion about this. I think every pull request that was created based on master, which would be

Re: [Discuss] Blog at pulsar website

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 > > ________

[Call for Contribution] Translating Pulsar Documentation

Hi all, Now the new Pulsar website has integrated Crowdin for localization. If anyone is interested in contributing translations to Pulsar documentation, feel free to join the Crowdin project https://crowdin.com/project/apache-pulsar and contribute translations there.

Re: [DISCUSS] New Pulsar Documentation Website

at 2:01 PM Sijie Guo wrote: > Hi all, > > Now the new website has all the content in-sync with existing website: > https://pulsar.incubator.apache.org/staging/ > > Since I am doing 2.1.0 release, I am planning to cut over the current > website to new website at the last step of

[ANNOUNCE] Apache Pulsar 2.1.0-incubating released

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

Re: [DISCUSS] New Pulsar Documentation Website

ity as well. > > Nice work @Chris. > > On Fri, Jul 27, 2018 at 2:18 PM, Sijie Guo wrote: > > > Hi all, > > > > In the past few weeks, Chris Kellogg has been working on a new Pulsar > > documentation website using Docusaurus <https://docusaurus.io/>. It

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

s between cgo client and native go client, as as what you pointed out there are things applied to cgo client don't apply to native go client. > Another goal worth > considering is consistent behavior between this client and the others > (Java, C++). > > > > > > On Mon

[Result] [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

The vote is now closed with 3 +1s and no -1s. Binding +1s * Dave Fisher * Justin Mclean * Jim Jagielski Thank you, Sijie On Wed, Jul 25, 2018 at 11:17 AM Sijie Guo wrote: > This is the 5th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > Link to the vote o

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

Can any people from IPMC help review and vote this release? Sijie On Wed, Jul 25, 2018 at 11:17 AM Sijie Guo wrote: > This is the 5th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > Link to the vote on dev@pulsar list: > https://lists.apache.

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

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

[DISCUSS] New Pulsar Documentation Website

Hi all, In the past few weeks, Chris Kellogg has been working on a new Pulsar documentation website using Docusaurus . It is a Facebook open source project, designed for easy to maintain open source documentation websites. It is a very popular and documentation-focused

[VOTE] Pulsar Release 2.1.0-incubating Candidate 5

This is the 5th release candidate for Apache Pulsar, version 2.1.0-incubating. Link to the vote on dev@pulsar list: https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E Pulsar is a highly scalable, low latency messaging

[RESULT] [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

19, 2018 at 4:43 PM Sijie Guo wrote: > This is the 5th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It introduces following main features: > > - Pulsar I/O: a serverless connector framework built on top of Pulsar > Functions. > - TieredStorage: off

Apache Jenkins Trigger Phrases

Hi all, I have updated the jenkins CI. now you can trigger individual jobs without rerun all tests. - `(re)run java8 tests` => for java8 tests - `(re)run cpp tests` => for cpp tests - `(re)run integration tests` => for integration tests "(re)test this please" will still trigger running all 3

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

any more review comments? - Sijie On Fri, Jul 20, 2018 at 1:13 PM Sijie Guo wrote: > Okay will remove it. > > But just to clarify, the KEYS file I put in the voting email is the one > used for releases, the one contains my KEY. Please use the one in voting > email to veri

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

KEYS here: > https://dist.apache.org/repos/dist/dev/incubator/pulsar/KEYS > > Probably that should be removed or updated from the release version. > > Regards, > Dave > > > On Jul 20, 2018, at 12:58 PM, Sijie Guo wrote: > > > > HI Dave, > > > > My k

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

cute goal > pl.project13.maven:git-commit-id-plugin:2.2.4:revision *(git-info)* on > project protobuf-shaded: *.git directory is not found! Please specify a > valid [dotGitDirectory] in your pom.xml* -> *[Help 1]* > > Regards, > Dave > > On Jul 19, 2018, at 4:43 PM, Si

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

HI Dave, My key is already there : https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Search "Sijie Guo" - Sijie On Fri, Jul 20, 2018 at 11:47 AM Dave Fisher wrote: > Hi Sijie, > > Please add your key to the KEYS file. > > Regards, > Dave >

Re: PIP 18: Pulsar SQL

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 P

Re: PIP 18: Pulsar SQL

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

[VOTE] Pulsar Release 2.1.0-incubating Candidate 5

This is the 5th release candidate for Apache Pulsar, version 2.1.0-incubating. It introduces following main features: - Pulsar I/O: a serverless connector framework built on top of Pulsar Functions. - TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3). - Stateful Function:

Re: PIP 18: Pulsar SQL

queries - Queries from users or groups should not overly impact other queries from other users or groups - Sijie On Thu, Jul 19, 2018 at 2:09 PM Sijie Guo wrote: > Great writeup, Jerry and Matteo! Can you share a google doc version of the > PIP? That might be better for people to c

Re: PIP 18: Pulsar SQL

Great writeup, Jerry and Matteo! Can you share a google doc version of the PIP? That might be better for people to comment on it. I am ccing users@ mailing list as well. We can also get feedback from pulsar users as well. - Sijie On Thu, Jul 19, 2018 at 12:44 PM Jerry Peng wrote: > Hi

Re: Release 2.1

branch 2.1 is cut and a new release candidate tag is created. so when you merge new PRs, use 2.2 now :) thanks, Sijie On Thu, Jul 19, 2018 at 9:57 AM Sijie Guo wrote: > Hi all, > > I am cutting 2.1 release now. If you have new PRs coming up, please label > them as 2.2. > >

Re: Release 2.1

/2172 and a followup > >> (not pushed yet, but ready to go when #2172 is in), which fix auth in > >> python based functions. > >> > >> -Ivan > >> > >> On Mon, Jul 16, 2018 at 11:07 PM, Sijie Guo wrote: > >> > We have cleared up mo

Re: SF Bay Area Apache Pulsar Meetup . July 10 2019

Thanks Yahoo folks for hosting the meetup! It was great to get together to look back at those features and production usage in the past year. How do people think about next meetup? e.g. location, time. Or maybe we can start a survey in the community about this :) - Sijie On Tue, Jul 3, 2018 at

Release 2.1

Hi all, Due the connector packaging issue, we delayed 2.1 release on fixing that. During this period, there are also other changes coming in. so I will suggest us still labelling the issues for 2.1 release, and I will recreate 2.1 branch from master once we resolve all the issues for 2.1 release.

Re: [Cancelled] [VOTE] Pulsar Release 2.1.0-incubating Candidate 4

ull the candidate. I want to > understand that this would be a regression from the last release. > > Best Regards, > Dave > > Sent from my iPhone > > > On Jun 29, 2018, at 3:13 PM, Sijie Guo wrote: > > > > Cancelled RC4. Connectors don't really work. > > &

[Cancelled] [VOTE] Pulsar Release 2.1.0-incubating Candidate 4

Cancelled RC4. Connectors don't really work. - Sijie On Fri, Jun 29, 2018 at 2:37 AM Sijie Guo wrote: > This is the 4th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milest

[VOTE] Pulsar Release 2.1.0-incubating Candidate 4

This is the 4th release candidate for Apache Pulsar, version 2.1.0-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/13?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are

[Cancel] [VOTE] Pulsar Release 2.1.0-incubating Candidate 3

Sorry have to cancel this RC again. Missed one cherry-pick : https://github.com/apache/incubator-pulsar/pull/2046#issuecomment-401286885 - Sijie On Thu, Jun 28, 2018 at 5:33 PM Sijie Guo wrote: > This is the 3rd release candidate for Apache Pulsar, version > 2.1.0-incubating. > &

[VOTE] Pulsar Release 2.1.0-incubating Candidate 3

This is the 3rd release candidate for Apache Pulsar, version 2.1.0-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/13?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are

[CANCELLED] [VOTE] Pulsar Release 2.1.0-incubating Candidate 2

Cancel the RC due to license issues. On Tue, Jun 26, 2018 at 6:53 PM Sijie Guo wrote: > This is the second release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/13?closed=1

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

Cancel the vote. There are still license issues due to version upgrades on 2.1. - Sijie On Tue, Jun 26, 2018 at 6:53 PM Sijie Guo wrote: > This is the second release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It fixes the following issues: > https://gi

[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:

[VOTE] Pulsar Release 2.1.0-incubating Candidate 2

This is the second release candidate for Apache Pulsar, version 2.1.0-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/13?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we

[CANCELLED] [VOTE] Pulsar Release 2.1.0-incubating Candidate 1

Cancel RC1 due to OpenSSL linking issues on the pre-built PRM/DEB packages. On Mon, Jun 25, 2018 at 4:24 PM Sijie Guo wrote: > This is the first release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It fixes the following issues: > https://github.com/apache/i

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 1

on, Jun 25, 2018 at 4:25 PM Sijie Guo wrote: > > > This is the first release candidate for Apache Pulsar, version > > 2.1.0-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/13?closed=1 > > > > **

[VOTE] Pulsar Release 2.1.0-incubating Candidate 1

This is the first release candidate for Apache Pulsar, version 2.1.0-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/13?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we

Re: Planning for release 2.1

FYI Cut branch-2.1. Starting the release process. On Thu, Jun 21, 2018 at 12:30 PM Sijie Guo wrote: > I am planning to cut the branch and start the release process tomorrow. > > If you have any items outstanding for 2.1 or would like them to be > included 2.1, please label th

Re: Planning for release 2.1

Sijie Guo wrote: > I am happy to contribute if no one else is working on that. > > - Sijie > > On Mon, Jun 18, 2018 at 12:01 PM Matteo Merli wrote: > >> As we are about to release 2.0.1, we have already a batch of new items >> ready to be released. Biggest tic

Re: [VOTE] Maintaining "Apache Pulsar" name

+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

Re: Non-serializable builders

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 fo

[ANNOUNCE] Apache BookKeeper 4.7.1 released

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

Re: Non-persistent topics

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: >

Re: Non-persistent topics

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 On Tue, Jun 19, 2018 at 12:22 PM Sijie Guo wrote: > Actually there is already an is

Re: Non-persistent topics

On Tue, Jun 19, 2018 at 12:15 PM Sijie Guo wrote: > I found the issue. So in 2.0 there is an optimization change on grouping > acknowledgements. The optimization change here > <https://github.com/apache/incubator-pulsar/commit/19dd2c502725e3b45e56541576508626c

Re: Non-persistent topics

ven client already receive them from the wire. Filing a github issue for it. - Sijie On Tue, Jun 19, 2018 at 11:27 AM Sijie Guo wrote: > Hi Geoffroy, > > Sorry for late response. I tried your sequence and observed same behavior. > so there might be something wrong there. I am looki

Re: Non-persistent topics

Hi Geoffroy, Sorry for late response. I tried your sequence and observed same behavior. so there might be something wrong there. I am looking into it now. - Sijie On Tue, Jun 19, 2018 at 11:13 AM wrote: > Le 2018-06-19 19:08, Ali Ahmed a écrit : > > Is the server version is both cases 2.0 ? >

Re: [ANNOUNCE] Apache Pulsar 2.0.1-incubating released

 On Tue, Jun 19, 2018 at 12:43 AM Matteo Merli wrote: > The Apache Pulsar team is proud to announce Apache Pulsar version > 2.0.1-incubating. > > This release fixes issues reported for 2.0.0-rc1-incubating. > Pulsar is a highly scalable, low latency messaging platform running on > commodity

Re: Planning for release 2.1

I am happy to contribute if no one else is working on that. - Sijie On Mon, Jun 18, 2018 at 12:01 PM Matteo Merli wrote: > As we are about to release 2.0.1, we have already a batch of new items > ready to be released. Biggest ticket items are: > * Connector framework > * Go client library >

CloudEvents

Hi all, cloudevents is a specification for describing event data in a common way. I wrote a transport binding proposal for pulsar - how to map pulsar messages into cloudevents specification. Here is a draft: https://gist.github.com/sijie/082c59e66b9ed175c1bb48466f3629f0

triage labels

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,

Re: Pulsar meetup in June/July

Date is July 10th > > Joe > > > > On Thu, Jun 7, 2018 at 4:55 PM, Sijie Guo wrote: > > > +1 go pulsar! > > > > - Sijie > > > > On Thu, Jun 7, 2018 at 4:49 PM Sanjeev Kulkarni > > wrote: > > > > > July 10th works for me

Re: Non-serializable builders

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: >

Re: Non-serializable builders

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

Re: [DISCUSSION] Podling name search

irst get the plane to take off. > I like this, strongly +1. #shipit > > On Thu, Jun 7, 2018 at 6:39 PM Sijie Guo wrote: > > > +1 for using the name "Apache Pulsar". > > > > - Sijie > > > > On Thu, Jun 7, 2018 at 5:01 PM Matteo Merli

Re: [DISCUSSION] Podling name search

+1 for using the name "Apache Pulsar". - Sijie 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

Re: Pulsar meetup in June/July

gt; > and its available on July 9th, 10th, or 13th . How does that sound? I > > need to reserve a firm date... > > > > My preference is for 10th [since its not a Monday or Friday :-) ] but > I'm > > fine with a whatever is convenient for all .. > > > > &

Re: [DRAFT] Pulsar Podling report June 2018

+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). > > > > >

Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 1

+1 (binding) Environment: MacOS 10.13.1 * check signatures, all are good. * Bin distribution - start standalone - test producer/consumer using pulsar-client and pulsar-perf * Src distribution - compile and unit tests - RAT check - start standalone - test producer/consumer

[ANNOUNCE] Jerry Peng and Sanjeev Kulkarni as Apache Pulsar committers and PPMC members

Greetings, The Apache Pulsar PPMC has voted to accept Jerry Peng (@jerrypeng) and Sanjeev Kulkarni (@srkukarni) as a Pulsar committer and PPMC member. Jerry and Sanjeev co-developed and contributed Pulsar Functions. They have dedicated themselves to pulsar community, reviewing PRs, joining

Re: Weirdness in jenkins build (tests not isolated as expected)

Gotcha! - Sijie On Mon, Jun 4, 2018 at 11:50 AM, Ivan Kelly wrote: > >> Two concurrent builds on the same machine will have different > >> workspaces (@2 or @3 will be appended to $WORKSPACE). > > > > I am not sure about that. If taking a look at the jenkins job output, the > > workspace is "

Planning for release 2.1

Hi all, It has been one month since we cutting 2.0 release. We have quite bunch of changes completed in the past month. These changes include: - Pulsar IO connector framework using pulsar functions - CPP Client catch up tasks - Tiered storage - Functions integration with schema registry I am

Re: Podling Report Reminder - June 2018

Hi all, We have a podling report due this Wednesday. Anyone wanna put up a draft? - Sijie On Sun, Jun 3, 2018 at 5:06 PM, wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to >

Re: Weirdness in jenkins build (tests not isolated as expected)

On Mon, Jun 4, 2018 at 4:42 AM, Ivan Kelly wrote: > > 1) the job is using `$WORKSPACE/.repository` as the maven local repo. > > 2) concurrent build is enabled > > 3) it is a freestyle build, including two maven runs. > > Two concurrent builds on the same machine will have different > workspaces

Re: Weirdness in jenkins build (tests not isolated as expected)

Not fully sure, but I guess the problem comes from concurrent build and two maven runs in integration tests. https://github.com/apache/incubator-pulsar/blob/master/.test-infra/jenkins/job_pulsar_precommit_integrationtests.groovy#L29

Re: Pulsar meetup in June/July

Any updates? - Sijie On Mon, Apr 30, 2018 at 7:29 PM, Joe F wrote: > I would expect people to volunteer and sign up... that's why I said "from > Pulsar users and developers". > > > Joe > > On Mon, Apr 30, 2018 at 6:44 PM, Dave Fisher > wrote: > > > Hi - > > > > What would be the agenda? > >

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

yes we need to update the website. > > On Fri, Jun 1, 2018 at 9:49 AM Sijie Guo wrote: > > > +1 (binding) > > > > Environment: MacOS 10.13.1 > > > > * check signatures, all are good. > > * Bin distribution > > - start standalone > > - tes

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

+1 (binding) Environment: MacOS 10.13.1 * check signatures, all are good. * Bin distribution - start standalone - test producer/consumer using pulsar-client and pulsar-perf * Src distribution - compile and unit tests - RAT check - start standalone - test producer/consumer

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

On Fri, Jun 1, 2018 at 9:41 AM, Dave Fisher wrote: > Hi - > > +1 (binding) > > Please remove the MD5 as these should no longer be generated. > Thanks Dave. I filed a github issue to take MD5 out of our website as well. https://github.com/apache/incubator-pulsar/issues/1891 > > Checked

Re: [ANNOUNCE] Apache Pulsar 2.0.0-rc1-incubating released

Awesome job, Matteo and the team! Congrats! - Sijie On Tue, May 29, 2018 at 5:53 PM, Matteo Merli wrote: > The Apache Pulsar team is proud to announce Apache Pulsar version > 2.0.0-rc1-incubating. > > This is the fifth Pulsar release after entering the Apache Incubator. > > Pulsar is a highly

Re: Release 4.7.1

/cc dev@pulsar.incubator.apache.org On Wed, May 23, 2018 at 5:21 PM, Sijie Guo <guosi...@gmail.com> wrote: > Hi all, > > It is about one month since 4.7.0 and there are bunch of bugs were > cherry-picked to branch-4.7. so it might be a good time to do a release for > 4.7

  1   2   >