What's the status of this VOTE thread?
Enrico
Il Ven 30 Lug 2021, 12:35 Enrico Olivelli ha scritto:
> -0 (non binding)
>
> - verified the signatures and checksums
> - apache RAT passes
> - run tests, on jdk8 on MacOs and Ubuntu, there are tests failures
> - run distri
Il Mer 4 Ago 2021, 04:49 丛搏 ha scritto:
> The vote passes with the following votes:
> - Yong Zhang (non binding)
> - Masahiro Sakamotoi (binding)
> - Nozomi Kurihara (binding)
> - PengHui Li (binding)
> - Enrico Olivelli (non binding)
>
Bo,
Thanks for running the release.
The proposal looks very interesting and useful. Thanks for bringing this up.
I wonder how we will be able to enforce such way of logging once we are
done with the switch.
There will be some education for contributors and committers about how to
use the Logger.
Enrico
Il Mer 4 Ago 2021, 05:52 Sh
Il Gio 5 Ago 2021, 20:11 Ivan Kelly ha scritto:
> Seems like all the feedback is positive. What's the process for moving
> the PIP to approved? I don't see anything on the wiki. Nor in the
> bylaws (where are they? they're not linked on site menu).
>
This is currently an open point :(
Probably
Hello,
In order to run the integration tests of Pulsar Adapters we need the
"integration tests" jar of Pulsar.
I have updated the Release process page for Pulsar and added
"-DintegrationTests" to the command line that deploys the artifacts to
Maven Central.
https://github.com/apache/pulsar/wiki/R
+1
great work
Enrico
Il giorno lun 9 ago 2021 alle ore 08:20 PengHui Li
ha scritto:
> I have copied to wiki page
> https://github.com/apache/pulsar/wiki/PIP-90%3A-Expose-broker-entry-metadata-to-the-client
>
> Thanks,
> Penghui
> On Aug 9, 2021, 11:57 AM +0800, dev@pulsar.apache.org, wrote:
>
+1
looking forward to the implementation
thanks
Enrico
Il giorno mar 10 ago 2021 alle ore 08:06 Yunze Xu
ha scritto:
> +1
>
> It makes sense to me. I also encountered TooManyRequests in topic lookup
> when there’re a lot of topics.
>
> It should be retriable instead of a simple error response
Congrats ! well deserved!
Enrico
Il giorno mar 10 ago 2021 alle ore 05:25 Guangning E
ha scritto:
> Congrats Rui
>
>
> Thanks,
> Guangning
>
> Yu Liu 于2021年8月10日周二 上午10:59写道：
>
> > Congrats Rui! Great job on all your hard work!
> >
> > On Tue, Aug 10, 2021 at 10:49 AM Jinfeng Huang
> > wrote:
Great !
thank you Cong Bo
Enrico
Il giorno mer 11 ago 2021 alle ore 08:33 Jinfeng Huang
ha scritto:
> Super excited to hear about it.
> Thank you very much for your efforts~
>
> Best Regards,
> Jennifer
>
>
> On Wed, Aug 11, 2021 at 12:35 PM Yu Liu
> wrote:
>
>> Hi Congbo,
>> Thanks for your g
Hello,
I have sent a PR in order to clean up the DefaultImplementation class and
make it simpler, in a way that we are no more using reflection for each
call to DefaultImplementation class.
Summary of the contents of the patch:
- introduce an interface, PulsarClientImplementationBinding, that defi
Hello,
How is the Presto work going ?
IIRC the plan was to remove it from the Pulsar code base and let it be
hosted at Trino.
If this is not going to happen within the 2.9.0 release timeline
(September?) I would prefer to upgrade to "Trino".
Probably we will have a downside problem that recent ver
; Our goal is still to get this completed as part of the 2.9 release.
>
Wonderful
Thanks
Enrico
>
> - Sijie
>
> On Fri, Aug 13, 2021 at 2:04 AM Enrico Olivelli
> wrote:
> >
> > Hello,
> > How is the Presto work going ?
> > IIRC the plan was to remove i
Matteo,
Overall the proposal looks good to me.
I have a couple of points, about the 'VOTE' and about what is subject to a
PIP or not.
I will add my comments inline below
Shall we need a "meta PIP" for this PIP ? Just joking, this discussion is
probably enough.
Thank you very much, we really neede
Matteo,
thank you for your clarification
I agree that having 3 +1 from PMC members is good for a PIP
I am +1 in the current form of this proposal.
Enrico
Il giorno gio 19 ago 2021 alle ore 21:35 Matteo Merli
ha scritto:
> On Thu, Aug 19, 2021 at 12:49 AM Enrico Olivelli
> wrote:
Hang,
thank you for being the release manager and trying to fix the problems.
This is an important change, and before adding it to a point release we
should be sure that we are not going to break compatibility.
I have two questions:
1) aren't we building the docker images on CI for every PR relat
rence between python 3.7 and python 3.8
>
> What's new in python3.8 compared to 3.7
> https://docs.python.org/3/whatsnew/3.8.html
>
> Python3.8.10 change log
> https://docs.python.org/release/3.8.10/whatsnew/changelog.html
>
> Thanks,
> Hang
>
> Enrico Olivel
Hello,
Currently we have the ability to add Protocol Handlers to the Pulsar
Broker, this is great, because you can add your code that uses internal
Pulsar APIs and implement your own protocols.
When you run Pulsar in k8s (and this is happening more and more) you need
to run the Pulsar proxy.
The P
nk it is a logical next step to add
>> support for protocol handlers in the proxy.
>>
>> I look forward to reviewing the PIP.
>>
>> - Michael
>>
>> On Fri, Aug 27, 2021 at 8:21 AM Enrico Olivelli
>> wrote:
>>
>> > Hello,
>> > Cur
+1
good idea to have a bot, otherwise I see much time wasted by you in always
asking the same things.
I appreciate very much your efforts
Probably this document fits well to be listed in the PIPs page, it is not
about code but about community/project management
@Matteo Merli what do you think?
Hang Chen,
I am evaluating the RC.
Are you able to push somewhere, on your Dockerhub account for instance, the
Docker Images?
This way it will be easier for people to test this RC using Kubernetes or
Docker ?
Thank you for driving this release
Enrico
Il giorno dom 29 ago 2021 alle ore 18:10 Lan
Hello Pulsar fellows,
I have prepared a PIP about adding support for Protocol Handlers
This is the GDoc
https://docs.google.com/document/d/1Hlc_BOpQTkWX8FgrvWSfk6h5xTQKMXnTcSuil0Nznrg/edit?usp=sharing
This is the PR for the implementation
https://github.com/apache/pulsar/pull/11838/files
I am
and forwards user identity (if needed) to the Broker
- performs authorization
The Proxy protocol handler does not access the BrokerService and cannot
access Pulsar broker internals
Enrico
>
> Thanks,
> Yunze
>
> > 2021年8月30日 下午4:47，Enrico Olivelli 写道：
> >
> > Hello Pul
MOP story may be similar
Enrico
>
>
> In MOP, some palace have use BrokerService, So we need change MOP or
> implement MOP for pulsar proxy PH again if we use MOP on pulsar proxy?
>
>
>
>
>
>
> - lan.liang
>
>
> On 08/30/2021 23:56，Enrico Olivelli wrote：
is responsible for other requests that require broker
> to be the topic owner, like PRODUCE and FETCH requests
> Right?
>
You are on the right way.
Probably it is better to discuss about KOP in a separate thread.
Enrico
Thank
> Yunze
>
> > 2021年8月30日 下午11:56，Enrico Olivel
ollowing commands.
>
> pulsar: `docker pull hangc0276/pulsar:2.8.1`
> pulsar-all: `docker pull hangc0276/pulsar-all:2.8.1`
> pulsar-dashboard: `docker pull hangc0276/pulsar-dashboard:2.8.1`
> pulsar-standalone: `docker pull hangc0276/pulsar-standalone:2.8.1`
>
> Thanks,
uot;
> *Date: *Monday, August 30, 2021 at 15:15
> *To: *"us...@pulsar.apache.org"
> *Cc: *Matteo Merli , "dev@pulsar.apache.org" <
> dev@pulsar.apache.org>, "fengtao...@bupt.edu.cn"
> *Subject: *Re: [Workflow] Introduce Bot to Improve Efficiency
>
>
Hang,
thanks for working on the License issue.
After working with Hang I realized that the Presto SQL build depends on the
JDK you use to build Pulsar.
If we build on JDK11 the results are good.
The package is still compatible at runtime with JDK8.
The problem is about Jetty HTTP2 ALPN Client. Mor
Jonathan,
Pulsar 2.8 (and 2.9) builds well on JDK8 and JDK11.
Tests are passing.
Developers can use both JDK8 and JDK11.
CI is running ONLY on JDK11 and we have a single workflow that runs some
tests on JDK8.
The binary tarballs work with JDK8 and JDK11
The Java client works with JDK8 and JDK11
Th
ead through the PIP. Looks good to me.
>
> - Michael
>
> On Mon, Aug 30, 2021 at 3:47 AM Enrico Olivelli
> wrote:
>
> > Hello Pulsar fellows,
> >
> > I have prepared a PIP about adding support for Protocol Handlers
> >
> > This is the GD
Hang,
I am not able to reproduce Massimiliano's problem
These commands pass on the stages sources unpacked by the source tarball,
on Ubuntu:
mvn clean install -DskipTests
mvn package -Pdocker -f docker/pom-xml
I have performed other tests and everything passed (apart from some flaky
test), but gi
Lari,
this is great work !
+1 for accepting this into the Pulsar project and for accepting new
adapters/client libraries.
My understanding is that Lari will contribute it as a separate repository.
My understanding is that it is fine to create a brand new repository and
let it be managed by the Pu
have to fix ASAP.
So if we do not include it in 2.8.1 we will follow up with a 2.8.2
immediately.
So overall it is better to include it and spend time only once to validate
the RC.
Enrico
>
> Thanks,
> Penghui
>
> On Thu, Sep 2, 2021 at 2:36 PM Enrico Olivelli
> wrote:
>
&g
Thu, Sep 2, 2021 at 8:12 PM Hang Chen wrote:
>
> > Hi Penghui,
> > I followed your steps to test the pulsar sql with jdk11, but I
> cannot
> > reproduce your situation. Would you please help verify your steps?
> >
> > Thanks,
> > Hang
>
write extensions
and do not let people be too creative.
>
> I would like to see these questions are answered before moving to a vote.
>
I hope that we can reach consensus on the need of this API.
because I see that there is a real need for making this happen.
It is the Pulsar momentu
+1 (binding)
- verified signatures/checksums
- verified apache rat on sources tarball
- built and run unit tests from sources, JDK11 on Ubuntu
- run smoke tests (not pulsar standalone, but real pulsar on local machine)
- built docker images from sources
great work
thank you Hang for bearing with m
Il Lun 6 Set 2021, 16:37 Massimiliano Mirelli <
massimilianomirelli...@gmail.com> ha scritto:
> Thank you for the rc.
>
> +1 (nonbinding)
>
>- Built from source code
>- Verified checksums and signatures
>- Run distributed system tests with Fallout.
>
> I had to:
>
>- chmod +x docke
Lin,
Il giorno mer 8 set 2021 alle ore 07:34 linlin ha
scritto:
> # Motivation
>
> There are many users who need to use tag messages. The implementation of
> this part has also been discussed before：
>
>
> https://lists.apache.org/list.html?*@pulsar.apache.org:lte=2y:Proposal%20for%20Consumer%20
(ping)
Il giorno ven 3 set 2021 alle ore 14:06 Enrico Olivelli
ha scritto:
> Sijie,
> Thanks for your questions, answers inline below.
>
> Il giorno gio 2 set 2021 alle ore 02:23 Sijie Guo ha
> scritto:
>
>> I would like to see the clarification between the broker
ings/protocol
handlers instead of doing that.
By the way I will be happy to drive this new effort if this is REALLY what
we want.
So I am convinced that for the short/mid term this PIP is the best choice
to help Pulsar adoption.
This PIP will unlock some great potential that otherwise will be
available o
very good
+1
I fixed a couple of typos in the wiki page
Enrico
Il giorno gio 9 set 2021 alle ore 08:58 丛搏 ha scritto:
> Hello,
> How are you?
> We have created a PIP.
>
> PIP 92: Topic policy across multiple clusters
>
>
> https://github.com/apache/pulsar/wiki/PIP-93%3A-Transaction-performance
Lin,
Il giorno mer 8 set 2021 alle ore 09:40 Lin Lin ha
scritto:
>
> > I also share this problem, because if you want to efficiently implement
> > message filtering you need to do it in the broker side.
> >
> > I am not sure that making the full Dispatcher pluggable is a good idea,
> > because t
Hello,
I apologise in advance, but I am still new to some of the procedures here.
I just noticed a new release of the Pulsar Helm Chart.
How does the release of the Helm chart work ?
Apparently this is something that is not released using the usual process.
Can anyone post some link to the proced
> pulsar image. For example: our recently released pulsar 2.8.1:
> https://github.com/apache/pulsar-helm-chart/pull/161
>
> --
> Thanks
> Xiaolong Ran
>
>
> Enrico Olivelli 于2021年9月10日周五 下午2:32写道：
>
> > Hello,
> > I apologise in advance, but I am still new
or
> pulsar-helm-chart The release processing flow, which is more in line with
> the specifications and operations of the Apache Way.
> --
>
> Thanks
> Xiaolong Ran
>
> Enrico Olivelli 于2021年9月10日周五 下午5:00写道：
>
> > Xiaolong,
> > Thanks for your information, very usef
Hello,
I would like to have the ability to store metadata about topics.
This would be very useful as with metadata you could add labels and other
pieces of information that would allow to define the purpose of a topic,
custom application level properties.
This feature will allow application level
help contributors to get their patch merge.
There are a few PIPs that have been partially merged, this is not a big
problem
as far as we have not introduced incomplete features.
Best regards
Enrico Olivelli
other comments ?
Enrico
Il giorno gio 9 set 2021 alle ore 09:15 Enrico Olivelli
ha scritto:
> Joe,
>
> Il giorno gio 9 set 2021 alle ore 04:31 Joe F ha
> scritto:
>
>> Enrico, my initial comment when you brought up PH was in relation to the
>> larger question
Il giorno lun 20 set 2021 alle ore 02:02 PengHui Li ha
scritto:
> Thank Bowen, In my opinion, the authorization information should be deleted
> after the topic been deleted no matter the topic is deleted automatically
> or manually. If the topic auto-creation and auto-deletion enabled, the new
>
a
major change).
It is better to enforce the planning instead of delaying the release.
Best regards
Enrico
Il giorno sab 18 set 2021 alle ore 14:53 PengHui Li ha
scritto:
> +1
>
> I'm checking some PRs which need review for now.
>
> Thanks,
> Penghui
>
> On Mon, Sep 1
Marvin,
Il Mar 21 Set 2021, 04:49 Zhengxin Cai ha scritto:
> Hi Pulsar Community,
>
> I'd like to propose that we introduce Maven Modernizer[1] plugin into
> Pulsar project.
> This plugin helps detecting uses of legacy APIs which can be replaced with
> modern APIs that are often more performant,
Hello,
I have to revert the Doc Bot because it looks like it needs more
permissions that what we have currently in the token we are using on GitHub
Currently CI in broker, every new PR will fail validation.
This is the commit that broke everything
https://github.com/apache/pulsar/commit/d4702ed17
Il giorno mer 22 set 2021 alle ore 14:33 Zhengxin Cai
ha scritto:
> Hi there,
>
> I'm not sure if this is worth a PIP in the sense that it's not trying to
> refactor existing or add new functionality which we might face trade off
> thus need detailed design and discuss
> Replacing code snippets w
Congrats
thank you for being the RM
Enrico
Il giorno mer 22 set 2021 alle ore 04:51 Anonymitaet _ <
anonymita...@hotmail.com> ha scritto:
> Congratulations on this new release! Thank you for your continuous effort!
>
>
>
> *From: *Jinfeng Huang
> *Reply-To: *"us...@pulsar.apache.org"
> *Date:
Hello,
it looks like we need to add a new GH token as GH secret in order to make
the documentation bot work.
the current token has not write privileges (is this statement correct?) and
cannot add labels and comments.
My plan is to:
1) create a new token
2) add it as GH secret
3) Allow the Doc bot
,
> > > > Michael
> > > >
> > > > On Sun, Sep 19, 2021 at 7:21 PM PengHui Li
> wrote:
> > > >
> > > > > Hi enrico
> > > > >
> > > > > +1, sorry I missed the email before. It should be a useful feature
&
dpoint in front of a Pulsar cluster anymore.
>
> Hence I don't think proxy PH is the right solution for the problems you are
> trying to solve. I would avoid introducing PH to proxy.
>
> - Sijie
>
> On Tue, Sep 14, 2021 at 8:02 AM Enrico Olivelli
> wrote:
>
> > ot
Hello,
Today I had to rename my PIP from PIP-93 to PIP-95 because PIP-93 was
picked up.
Then I realised that PIP95 already exists on GitHub, then I moved to PIP-97.
There are multiple PIP-95 on the Wiki page.
https://github.com/apache/pulsar/wiki
We need a way to assign new PIP ids
What about s
Eron,
I missed your initial message, thanks for bumping up this thread.
I read the proposal and I am +1
You should run a VOTE now
Enrico
Il Ven 24 Set 2021, 20:21 Eron Wright ha
scritto:
> Re-upping this discussion. Seems like the community is ready to accept the
> proposal, any objections?
+1
Thanks
Enrico
Il giorno ven 24 set 2021 alle ore 21:41 Eron Wright
ha scritto:
> Dear Pulsar community, please vote now on PIP 95:
> https://github.com/apache/pulsar/issues/12040
>
> Note that there are numerous proposals that have been labeled as PIP 95.
> Sorry for the inconvenience.
>
> -
e concerns about the
proposal,
but on the other hand I did not see many other opinions.
I would like to run a VOTE early next week
Enrico
Il giorno gio 23 set 2021 alle ore 14:09 Enrico Olivelli <
eolive...@gmail.com> ha scritto:
> Hello everyone,
> I have created a new version of
ss.
>
Agreed
Thanks
Enrico
> > Does anyone volunteer to clean up the PIP list page ?
> Once we settle on a protocol, we will need to clean up, as now we have
> two PIP 97s.
>
> Thanks,
> Michael
>
> On Thu, Sep 23, 2021 at 9:51 AM Enrico Olivelli
> wrote:
> &
Michael
The proposal makes sense to me.
I don't have other questions
Enrico
Il Sab 25 Set 2021, 00:06 Michael Marshall ha
scritto:
> Hi Pulsar Community,
>
> It's great to see so many active PIP emails going around on our ML. :)
>
> Following up on my PIP for Asynchronous Authentication Provid
Hello everyone,
I would like to start a VOTE for PIP-99 Pulsar Proxy Extensions
This is the PIP-99
https://github.com/apache/pulsar/issues/12157
This is the PR for the implementation (still draft, I will complete it
after the PIP is approved)
https://github.com/apache/pulsar/pull/11838
Please V
I have created a INFRA ticket
https://issues.apache.org/jira/browse/INFRA-22368
I will provide a personal token
If anyone has a better idea please chime in
Any help is really appreciated
Enrico
Il giorno gio 23 set 2021 alle ore 08:59 Enrico Olivelli <
eolive...@gmail.com> ha s
I agree that we must ensure that every pending callback must be completed
eventually (timeout or another error is not a problem),
because we cannot let the client application hang forever.
I believe that the application can perform a flush() explicitly and also
wait for every callback to be execute
+1 (binding)
Enrico
Il Gio 30 Set 2021, 06:08 Yunze Xu ha
scritto:
> Hi folks,
>
> It has been about two weeks since I opened the PIP-96 issue and the design
> has
> changed a lot. Thanks a lot for @eolivelli's suggestions. I think now it's
> time
> to start a vote.
>
> PIP-96 issue: https://g
Penghui,
Il Gio 30 Set 2021, 06:10 PengHui Li ha scritto:
> Hi all,
>
> Hope you are well, currently, we are exposing the topic metrics with an
> open one label topic which
> is the complete topic name such as
> `persistent://public/default/xxx-partition-0`, but as
> https://github.com/apache/pu
u for this good discussion
Regards
Enrico
Il giorno mer 29 set 2021 alle ore 10:03 Hang Chen ha
scritto:
> +1
>
> Thanks,
> Hang
>
> Lin Lin 于2021年9月29日周三 下午3:57写道：
> >
> >
> >
> > On 2021/09/27 09:00:52, Enrico Olivelli wrote:
> > > Hello ev
+1 (binding)
Enrico
Il Gio 30 Set 2021, 19:54 Matteo Merli ha scritto:
> LGTM +1
>
>
> --
> Matteo Merli
>
>
> On Mon, Sep 27, 2021 at 1:43 PM Michael Marshall
> wrote:
> >
> > Hi Pulsar Community,
> >
> > I would like to start a VOTE for PIP-97 Asynchronous Authentication
> Provider.
> >
>
Great work!
Overall the proposal looks good to me.
But I think we are missing these topics:
- how to enable this feature (new broker configuration flag?)
- how to handle old consumer connecting to a system with watermarks (we
should not deliver the watermark events?)
- tooling to support operation
Yunze
You can move the PIP to Approved and copy it to the Wiki.
Now that it is approved we can review and finally merge the PR
Enrico
Il Lun 4 Ott 2021, 08:03 Yunze Xu ha scritto:
> I see there’re already three +1 now. Here’s the related PR:
>
> https://github.com/apache/pulsar/pull/12088 <
>
Hello everyone,
I am going to cut the first RC of Pulsar 2.9.0 on Wednesday, in Europe
morning.
There are a few approved PIP that needs review and merging.
Please let me know for any blocker.
Tomorrow, Tuesday, I will move every pending issue and PR scheduled for
2.9.0 to 2.10.0.
If the owner o
Hello folks,
It has been quite some time since the latest releases of branch 2.6 and 2.7.
We should cut a release.
Probably we should also start a discussion about sending 2.6 to EOL as we
are releasing 2.9.0.
I am following the release for 2.9,
is there any volunteer to drive a release for 2.7
Michael,
I will take care of copying the PIP doc to the Wiki tomorrow
Congrats for your first PIP
Enrico
Il Lun 4 Ott 2021, 16:48 Michael Marshall ha
scritto:
> Hello,
>
> We can close the VOTE now and mark PIP-97 as Approved.
>
> The implementation is not ready for review, so we should wait u
Hello,
I am creating the release notes for Pulsar 2.9.0.
Apparently there is no export tool in GitHub that is able to export the
list of PRs by filtering it by milestone.
It looks like it is possible to do such export by label.
So my plan is to add release/2.9.0 to all the PRs in 2.9.0 milestone
de this PR for 2.9.0
> https://github.com/apache/pulsar/pull/11325
>
> I just pinged for review.
>
> Thanks
>
> From: Enrico Olivelli
> Date: 2021-10-04 15:01
> To: Dev
> Subject: Cutting 2.9.0 RC - final call
> Hello everyone,
> I am going to cut the first RC of P
+1 (binding)
Enrico
Il Ven 8 Ott 2021, 00:15 Rajan Dhabalia ha scritto:
> I would like to start voting on the PIP.
> PIP:
> https://github.com/apache/pulsar/wiki/PIP-100:-Pulsar-pluggable-topic-factory
>
> PR: https://github.com/apache/pulsar/pull/12235
>
> Thanks,
> Rajan
>
> On Tue, Sep 28, 2
critto:
> Hi，
>
> Please consider to include this PR for 2.9.0
> https://github.com/apache/pulsar/pull/11325
>
> I just pinged for review.
>
> Thanks
>
> From: Enrico Olivelli
> Date: 2021-10-04 15:01
> To: Dev
> Subject: Cutting 2.9.0 RC - final call
> Hel
Dave,
Thanks for pointing this out.
I had sent a similar message a couple of weeks ago regarding the helm chart.
I am not sure that we can recover past releases.
But I believe that we can enforce a better process for the next releases of
any artifact/sub project of Pulsar.
Il Ven 8 Ott 2021, 18:
is now 2.10.0-SNAPSHOT.
I will create branch-2.9 and reset the version in order to have clean git
history
Enrico
Il Ven 8 Ott 2021, 08:39 Enrico Olivelli ha scritto:
> Hello 18896728...@139.com
> (Please add a signature next time)
>
> I am sorry but your feature looks cool but it is
Any idea?
Enrico
Il Mer 6 Ott 2021, 15:52 Enrico Olivelli ha scritto:
> Hello,
> I am creating the release notes for Pulsar 2.9.0.
>
> Apparently there is no export tool in GitHub that is able to export the
> list of PRs by filtering it by milestone.
>
> It looks like it i
Masahiro,
I suggest to create a .tar.gz file with the contents of the release, only
source files
and copy it to the staging repository
https://dist.apache.org/repos/dist/dev/pulsar/
No need to add commits to the repo
I believe that if you do this we can continue on the VOTE
We should also updat
ase.
Best regards
Enrico Olivelli
+1 (binding)
great work !
Enrico
Il giorno mer 13 ott 2021 alle ore 08:34 linlin ha
scritto:
> Hi Pulsar Community,
>
> I would like to start a VOTE for PIP - Support pluggable entry filter in
> Dispatcher.
>
> The issue for this PIP is here:
> https://github.com/apache/pulsar/issues/12269
>
>
Amar,
Thanks for your contribution
I approved your PR, waiting for another reviewer
Cheers
Enrico
Il Gio 14 Ott 2021, 13:52 Amar Prakash Pandey ha
scritto:
> Hello everyone,
>
> I have opened a PR in which I have added the Maven Modernizer plugin in
> the pulsar-proxy module to enforce we move
good proposal.
I support it.
I left a comment on the issue, about having a way to configure this from
configuration parameters and not by passing a Java object
Enrico
Il giorno ven 15 ott 2021 alle ore 09:59 r...@apache.org <
ranxiaolong...@gmail.com> ha scritto:
> Thanks PenghuiLi, I will try
still see 2 missing PRs for PIP-85.
I am waiting for them, then I will move forward.
If there are no other API and protocol changes regarding transactions, any
other "problem" may be fixed in 2.9.1
Enrico
>
> --
> Thanks
> Xiaolong Ran
>
> Enrico Olivelli 于2021年10
Hello,
I have forked branch-2.9 (for the third time), any change you commit to
master branch won't be released in 2.9.0.
I am going to prepare a RC, so expect a VOTE email to be sent on Monday (I
won't do this in the weekend, in order to let more people participate in
the VOTE).
This is the PR to
I found that I had an outdated version of "gh" (Github cli tool)
The command below works well to create automatically the list of PRs is a
milestone.
I will update the release procedure
Enrico
gh pr list --search 'milestone:2.9.0 is:closed' -L 600
draft:
https://github.com/apache/pulsar/pull/12425
Please download the source package, and follow the README to build
and run the Pulsar standalone service.
Enrico Olivelli
Chris,
Il Gio 21 Ott 2021, 04:09 Chris Kellogg ha scritto:
> Hello,
>
> It's been a while since the last go client release (July 25th). There have
> been many fixes that have gone in since then and I think it's time for a
> new release.
>
Good idea
+1
Enrico
> I would like to volunteer to c
Hello,
We recently activated the Doc Bot on GitHub, to help people tag
properly the PRs.
It is using my account, so it LOOKS LIKE I am adding comments about the
need for documentation.
We (with Yu Liu and Tao Feng) are working on a fix for this.
We would probably need some Apache Pulsar BOT user
> > - verified pub/sub and java functions
> > - verified connectors
> > - verified stateful functions
> >
> > Hideaki Oguni
> > Yahoo Japan Corp.
> > E-mail: hog...@yahoo-corp.jp
> >
> > -Original Message-
> > From: Enrico Olivelli
repo/local cache, but not for this release.
Great catch Matteo
Enrico
.
>
>
> --
> Matteo Merli
>
>
> On Fri, Oct 22, 2021 at 2:53 AM Enrico Olivelli
> wrote:
> >
> > Il giorno ven 22 ott 2021 alle ore 07:31 Matteo Merli <
> > matteo.me...@gmail
Devin,
Il Lun 25 Ott 2021, 23:05 Devin Bost ha scritto:
> I've occasionally run into situations where I needed a list of all the
> topics in a cluster.
> If I want to submit a PR to add something to one of the endpoints to return
> a list of all topics in a cluster, what part of the API should t
Pulsar's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS
Release notes draft:
https://github.com/apache/pulsar/pull/12425
Please download the source package, and follow the README to build
and run the Pulsar standalone service.
E
+1
Enrico
Il giorno mer 27 ott 2021 alle ore 13:39 PengHui Li ha
scritto:
> +1
>
> On Wed, Oct 27, 2021 at 4:22 PM linlin wrote:
>
> > Hi all,
> >
> > I hope you've all been doing well. It has been more than one month since
> we
> > released the Apache Pulsar 2.8.1. We have a lot of fixes alre
Thank you Melissa
Enrico
Il giorno ven 29 ott 2021 alle ore 00:50 Melissa Logan <
meli...@constantia.io> ha scritto:
> Thanks to all who voted during the 72+ hour window for lazy consensus.
> This time concept #1 was the winning design with three votes, followed
> by #3b (two votes) and #2 (one
Il Ven 29 Ott 2021, 21:27 Dave Fisher ha scritto:
> Hi -
>
> > On Oct 29, 2021, at 12:02 PM, Matteo Merli wrote:
> >
> > The Pulsar website is getting published through a CI job that updates
> > the generated HTML files and commits them in the Pulsar repo, in a
> > separate branch ('asf-site').
+1 (binding)
Thanks
Enrico
Il Lun 1 Nov 2021, 09:50 PengHui Li ha scritto:
> I would like to start a VOTE for PIP 106: Negative acknowledgment backoff
>
> The issue for this PIP is here
>
> https://github.com/apache/pulsar/issues/12379
>
> Please VOTE within 72 hours.
>
> - Penghui
>
501 - 600 of 982 matches
Mail list logo
