+1 (binding)
On Tue, Mar 14, 2023 at 8:43 AM Matteo Merli wrote:
> +1 (binding)
>
>
> --
> Matteo Merli
>
>
>
> On Tue, Mar 14, 2023 at 8:29 AM Asaf Mesika wrote:
>
> > Hi,
> >
> > I would like to start the vote on PIP-249: Pulsar website redesign.
> >
> > PIP link: https://github.com/apache/p
Hi, all the Pulsar community members,
Pulsar Summit San Francisco 2022 CFP is open now! It will be our *first-ever
in-person Pulsar Summit *in San Francisco! We're glad to invite you to
share your experience and add up to the wonderfulness.
As a speaker, you will receive the chance to demonstrate
very much for the response and interest! I will post an update
> about the track as soon as I have one.
> >
> > Thanks
> > Sharan
> >
> > On 2022/03/15 23:59:46 Sijie Guo wrote:
> > > Sharan,
> > >
> > > I think it is a very gr
Sharan,
I think it is a very great idea to have a performance engineering track.
Some committers and I are definitely interested in contributing talks to
this track.
- Sijie
On Fri, Mar 11, 2022 at 4:44 AM sharanf wrote:
> Hi All
>
> The call for tracks for ApacheCon NA is open. There is a sug
Congrats!
Rui - Thank you for driving this important fix for the license issue!
- Sijie
On Tue, Mar 15, 2022 at 2:10 AM Rui Fu wrote:
> The Apache Pulsar team is proud to announce Apache Pulsar Go Client
> version 0.8.1.
>
> Pulsar is a highly scalable, low latency messaging platform running o
Best wishes to all the female contributors!
- Sijie
On Tue, Mar 8, 2022 at 9:00 AM Yu wrote:
> Dear Pulsar female contributors,
>
> Success doesn’t come easy and women never give up. Thanks for bringing so
> much love and support to the Pulsar community. And every man needs a
> woman when his l
Yu, thank you for driving this effort! Great to see a proposal focusing on
this! +1
On Fri, Mar 4, 2022 at 2:59 AM Yu wrote:
> Hi Pulsarers,
>
> For Pulsar release notes [1], we had issues below for a long time.
>
> - All contents are on a single Pulsar release note page. No navigations.
> It's
+1
On Sun, Mar 6, 2022 at 6:46 PM r...@apache.org
wrote:
> +1
>
> --
> Thanks
> Xiaolong Ran
>
> PengHui Li 于2022年3月5日周六 18:10写道：
>
> > +1
> >
> > Penghui
> >
> > On Sat, Mar 5, 2022 at 4:58 AM Matteo Merli
> > wrote:
> >
> > > +1 Thanks Rui, we should eliminate the GPL dependency ASAP.
> > >
i, Feb 18, 2022 at 1:07 AM Sijie Guo wrote:
>
> > Maybe we should roll back to the old website first.
> >
> > - Sijie
> >
> > On Thu, Feb 17, 2022 at 8:33 AM Sijie Guo wrote:
> >
> > > Remove users@
> > >
> > > Yu - I have rece
The website has been rolled back to the old one.
- Sijie
On Thu, Feb 17, 2022 at 12:37 PM Lari Hotari wrote:
> Change to roll back Apache Pulsar Helm chart publishing to new site:
> https://github.com/apache/pulsar-helm-chart/pull/234
>
> -Lari
>
> On 2022/02/17 19:44:
https://github.com/apache/pulsar-site/pull/3
https://github.com/apache/pulsar/pull/14356
Changes to roll back the website.
- Sijie
On Thu, Feb 17, 2022 at 11:30 AM Sijie Guo wrote:
> Hi all,
>
> All the Pulsar links out there (Google, Stackoverflow, etc) are broken. I
> am se
Hi all,
All the Pulsar links out there (Google, Stackoverflow, etc) are broken. I
am sending PRs to rollback the website push.
- Sijie
+1
On Thu, Feb 17, 2022 at 3:49 AM Guangning E wrote:
> Recently many users want to use the oauth2 feature based on the node js
> client. I've added this feature, so I'd like to start a release for the
> pulsar node js 1.6.0 client.
>
>
>
>
> Thanks,
> Guangning
>
Maybe we should roll back to the old website first.
- Sijie
On Thu, Feb 17, 2022 at 8:33 AM Sijie Guo wrote:
> Remove users@
>
> Yu - I have received quite a few questions about broken links.
>
> https://pulsar.apache.org/docs/en/security-jwt/ <- This is broken.
>
> I
sar website, do not hesitate to
> add it here [2], thanks.
>
> [1] https://github.com/apache/pulsar/pull/14344
> [2]
>
> https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#bookmark=id.86uprmy9cv2w
>
>
> On Thu, Feb 17, 2022 at 12:42 PM
tch today is causing this
> exception, we should update the helm chart ci to fix this issue, will take
> a look at it later
>
> Thanks,
> Guangning
>
> Sijie Guo 于2022年2月17日周四 12:52写道：
>
> > I send a notice to users@ mailing list and #general channel about the
> >
Hi everyone,
Just want to let everyone know that the Pulsar Helm Charts repo is
temporarily down due to the new Pulsar website push. The
`charts/index.yaml` was not added to the new Pulsar site. So if you are
using the helm command to pull the charts, it will fail. A bunch of the
committers is loo
I send a notice to users@ mailing list and #general channel about the
situation.
- Sijie
On Wed, Feb 16, 2022 at 8:46 PM Sijie Guo wrote:
> Hi all,
>
> I think the new website push has broken the Pulsar Helm Chart repo.
>
> We might need to take a look at how to fix it.
>
> - Sijie
>
Hi all,
I think the new website push has broken the Pulsar Helm Chart repo.
We might need to take a look at how to fix it.
- Sijie
Hi Yu,
Thank you and all the other contributors for all the great work! Well done.
- Sijie
On Wed, Feb 16, 2022 at 8:04 PM Yu wrote:
> Thanks for your quick feedback, Penghui and Dianjin.
>
> As mentioned in the last email, "*...**there are some known issues (eg.
> localized pages and some CLI
I don't think we should expose this feature flag on the client-side.
Ideally, people shouldn't be aware of partitioned vs non-partitioned.
- Sijie
On Wed, Feb 16, 2022 at 1:37 AM Enrico Olivelli wrote:
> Ping
>
> Il Dom 13 Feb 2022, 11:49 Enrico Olivelli ha
> scritto:
>
> > Hello,
> > I have a
5da0f95794259694cc781e8960b7e52fac06b
>
> On Thu, Jan 6, 2022 at 7:00 PM Sijie Guo wrote:
> >
> > Is Functions being verified?
> >
> > - Sijie
> >
> > On Wed, Jan 5, 2022 at 11:26 AM Michael Marshall
> > wrote:
> >
> > > PR 13376 is
Is Functions being verified?
- Sijie
On Wed, Jan 5, 2022 at 11:26 AM Michael Marshall
wrote:
> PR 13376 is ready for review, PTAL.
>
> What approach should we take regarding docker image size?
> I propose providing a minimal image along with documentation
> on how to add your own debugging tool
The fundamental problem I see is that we don't have a proper helm chart
release and we don't have good versioning guidance.
Chart should have its own version, which is independent of the Pulsar
version.
Also, we need to provide a guide to the community - most of the time, you
don't need to upgrad
I believe 48 hours vote is only for PIP, which was agreed in the dev@.
For other activities, this project follows the ASF 72 hours rule.
- Sijie
On Mon, Jan 3, 2022 at 8:17 PM Dave Fisher wrote:
> Yes please! I did not notice that.
>
> Personally I would be ok with 72 hours lazy consensus, but
+1 ThresholdShedder is a much better policy
On Tue, Jan 4, 2022 at 6:24 AM Hang Chen wrote:
> https://github.com/apache/pulsar/issues/13340
>
> Pasted below for quoting convenience.
>
>
> ### Motivation
> The ThresholdShedder load balance policy since Pulsar 2.6.0 by
> https://github.com/ap
+1
On Wed, Jan 5, 2022 at 12:12 AM Ran Gao wrote:
> +1
>
> Best,
> Ran Gao
>
> On 2022/01/04 03:34:33 PengHui Li wrote:
> > This is the voting thread for PIP-130. It will stay open for at least 48
> > hours.
> >
> > https://github.com/apache/pulsar/issues/13528
> >
> > Pasted below for quoting c
Can you clarify what is the main change? I see most of the changes are done
in the CI part.
- Sijie
On Tue, Jan 4, 2022 at 1:41 AM Lari Hotari wrote:
> Hi all,
>
> Currently k8s 1.14 version is used in CI to verify the Helm chart changes.
>
> k8s 1.14 became end-of-life 2019-12-11 , over 2 year
+1.
All make sense to me!
We probably need to move to the feature frozen stage in order to cut a
release at the end of January.
- Sijie
On Sun, Dec 26, 2021 at 8:46 PM PengHui Li wrote:
> Hi, everyone
>
> I hope you’ve all been doing well. I would like to start an email thread to
> discuss fe
Hi Francisc,
The 2.8.2 image is there:
https://hub.docker.com/layers/apachepulsar/pulsar/2.8.2/images/sha256-d538416d5afe03360e10d5beb44bdad33d7303d137fc66c264108426875f61c6?context=explore
- Sijie
On Thu, Dec 30, 2021 at 8:15 AM Francisc Florian Munteanu <
francisc.florian.munte...@infovista.co
Agree to have a vote to keep a record.
- Sijie
On Mon, Jan 3, 2022 at 3:40 PM 陳智弘 wrote:
> I think having a vote and quickly announce the EOF of 2.6.x will be better
> to the community.
>
>
> Dave Fisher 於 2022年1月4日 週二 06:06 寫道：
>
> > I don’t think we need a VOTE. Let’s do this by LAZY CONSENS
Thanks Yu and many contributors for the hard work on documentation!
Happy New Year!
- Sijie
On Fri, Dec 31, 2021 at 3:07 AM Yu wrote:
> Hi Pulsar enthusiasts,
>
>
> With 2022 knocking on our doors, I would like to take this opportunity to
> express sincere gratitude to you for making what Puls
Sorry. When you say "we discussed", who are "we"? Is it DataStax?
I believe we want to keep SQL until the code change lands in Trino. Because
there are still users using this component.
- Sijie
On Tue, Dec 21, 2021 at 11:34 PM Enrico Olivelli
wrote:
> Lari,
>
> Il giorno mer 22 dic 2021 alle o
+1
On Tue, Dec 21, 2021 at 3:49 PM Matteo Merli wrote:
> This is the voting thread for PIP-117. It will stay open for at least 48h.
>
> https://github.com/apache/pulsar/issues/13302
>
>
>
> ## Motivation
>
> Pulsar standalone is the "Pulsar in a box" version of a Pulsar cluster,
> where
> a
+1
On Tue, Dec 21, 2021 at 3:59 PM Matteo Merli wrote:
> This is the voting thread for PIP-123. It will stay open for at least 48h.
>
> https://github.com/apache/pulsar/issues/13346
>
>
> -
> ## Motivation
>
> For a very long time, we have included a CLI command to start the ZooKeeper
>
+1
On Tue, Dec 21, 2021 at 3:22 PM Matteo Merli wrote:
> https://github.com/apache/pulsar/issues/13304
>
> Following the discussion, I have updated the proposal to also include
> the deprecation and renaming of the config setting name to
> `metadataSessionExpiredPolicy`.
>
>
>
> ---
> ## Mot
+1
On Tue, Dec 21, 2021 at 3:23 PM Matteo Merli wrote:
> This is the voting thread for PIP-119. It will stay open for at least 48h.
>
> https://github.com/apache/pulsar/issues/13305
>
> ---
>
> ## Motivation
>
> The consistent hashing implementation to uniformly assign keys to consumers
+1
On Wed, Dec 22, 2021 at 2:08 PM Enrico Olivelli wrote:
> +1 (binding)
>
> Enrico
>
> Il Mer 22 Dic 2021, 16:58 Michael Marshall ha
> scritto:
>
> > +1
> >
> > - Michael
> >
> > On Wed, Dec 22, 2021 at 6:10 AM Hang Chen wrote:
> > >
> > > +1
> > >
> > > Thanks,
> > > Hang
> > >
> > > PengHui
+1
On Tue, Dec 14, 2021 at 11:20 AM Matteo Merli wrote:
> https://github.com/apache/pulsar/issues/13306
>
>
> Pasted below for quoting convenience.
>
>
>
>
> ## Motivation
>
> In Pulsar 2.8, we have introduced a setting to control the amount of memory
> used by a client instance.
>
> ``
+1
On Tue, Dec 14, 2021 at 10:15 AM Matteo Merli wrote:
> Pasted below for quoting convenience.
>
>
>
>
> ## Motivation
>
> The consistent hashing implementation to uniformly assign keys to consumers
> in the context of a KeyShared subscription, was introduced in
> https://github.com/ap
+1
On Tue, Dec 14, 2021 at 10:03 AM Matteo Merli wrote:
> https://github.com/apache/pulsar/issues/13304
>
>
> Pasted below for quoting convenience.
>
> ---
>
>
> ## Motivation
>
> After all the work done for PIP-45 that was already included in 2.8 and 2.9
> releases, it enabled the concept o
+1
On Tue, Dec 14, 2021 at 9:18 AM Matteo Merli wrote:
> https://github.com/apache/pulsar/issues/13302
>
> Copying here for quoting convenience
>
>
>
>
>
> ## Motivation
>
> Pulsar standalone is the "Pulsar in a box" version of a Pulsar cluster,
> where
> all the components are started with
12:44 PM Joshua Eric wrote:
>
> > That is an additional problem, that a PMC member doesn’t see an issue
> with
> > an SN employee promoting a new SN hire.
> >
> > At least half a dozen people join the community daily. Why aren’t we
> > celebrating all of them? No of
I have updated the blog post in
https://github.com/apache/pulsar/pull/13274/files
*If upgrading is not an option, you may also mitigate by adding
`-Dlog4j2.formatMsgNoLookups=true` to the `PUSLAR_EXTRA_OPTS` in the
`configData` section for proxy, broker, bookkeeper, zookeeper,
auto-recovery, and r
ocess.
- Sijie
On Mon, Dec 13, 2021 at 10:04 AM Dave Fisher wrote:
>
>
> > On Dec 13, 2021, at 9:57 AM, Sijie Guo wrote:
> >
> > I am fine with doing 2.9.1.
> >
> > I am trying to understand what happened between released 2.9.0 and
> > announcing it.
gt; > https://downloads.apache.org/pulsar/pulsar-2.9.0/
> >
> > (2) we have published 2.9.0 artifacts through maven central. They don’t
> > let anyone republish versions.
> >
> > There are no do overs on versions. We simply cannot redo 2.9.0 at this
> > moment.
&
h maven central. They don’t
> > let anyone republish versions.
> >
> > There are no do overs on versions. We simply cannot redo 2.9.0 at this
> > moment.
> >
> > All the best,
> > Dave
> >
> > Sent from my iPhone
> >
> > > On
My take is - if we haven't announced 2.9, I would suggest just redoing the
2.9.0 release.
- Sijie
On Sun, Dec 12, 2021 at 6:35 PM Hang Chen wrote:
> I am a little confused about why we should skip 2.9.0 and not continue
> to release 2.9.0 by including the critical bug fixes. In fact, the
> Puls
hing they could to make Confluent == Kafka. Great for Confluent,
> terrible for the community.
>
> SN != Pulsar
>
> On Dec 10, 2021 at 7:25:29 PM, Sijie Guo wrote:
>
> > Chris and Dave,
> >
> > Thank you for bringing the concern up. However, I don’t think the con
; > If you want Ford Motor Company as a customer, you should join my Ford
> > Ambassador Program. Ford would have a problem with that, and so should
> the
> > PMC of Apache Pulsar.
> >
> > This is exactly what Confluent started doing with the Kafka community.
> They
>
ls the
> roadmap and that the way to get involved and help shape the technology is
> by engaging with SN via their Ambassador program.
>
> On Fri, Dec 10, 2021 at 1:47 PM Dave Fisher wrote:
>
> >
> > > On Dec 9, 2021, at 3:24 PM, Sijie Guo wrote:
> > >
> &g
Dec 10, 2021, at 11:10 AM, Sijie Guo wrote:
> >
> >> I also think it is a misuse of the developer list to specifically
> announce
> > new community members that just so happen to be recent SN hires.
> >
> > What do you mean by "announce new community mem
Dave.
>
> I also think it is a misuse of the developer list to specifically announce
> new community members that just so happen to be recent SN hires.
>
> On Dec 9, 2021 at 3:24:29 PM, Sijie Guo wrote:
>
> > Dave - I don't think SN presents the community. We just shared o
+1
On Thu, Dec 9, 2021 at 6:27 AM Narayanan, Madhavan
wrote:
> Hi Pulsar Community,
>
>
>
> I would like to start a VOTE on the Pulsar Broker extensions for operators
> (PIP 106).
>
>
>
> The issue for PIP 106 is here:
> https://github.com/apache/pulsar/issues/12858
>
> And the prototype impleme
atus, the update has been done.
> >
> > Best,
> > Dianjin Wang
> >
> >
> > On Thu, Dec 9, 2021 at 2:34 PM Sijie Guo wrote:
> >
> >> Hi Dave,
> >>
> >> Will follow up tomorrow morning (Pacific Time).
> >>
> >> - Sijie
&
> Best Regards,
> Dave
>
> Sent from my iPhone
>
> > On Dec 8, 2021, at 9:24 PM, Sijie Guo wrote:
> >
> > Dave,
> >
> > I think that is a mistake. We already caught it. Dianjin is fixing it.
> >
> > - Sijie
> >
> >> On Wed, Dec
Dave,
I think that is a mistake. We already caught it. Dianjin is fixing it.
- Sijie
On Wed, Dec 8, 2021 at 11:41 AM Dave Fisher wrote:
> This is great news!
>
> However the ending of the blog post [1] does not follow the Apache Way
>
> This bullet point is misleading and serves to split the c
+1
On Wed, Dec 8, 2021 at 8:37 PM Masahiro Sakamoto
wrote:
> Hi Team,
>
> I'm planning to release v1.5.0 of the Pulsar Node.js client next week as
> some bug fixes have been merged to master.
> If you have any comments on this, please reply to this email.
>
> Regards,
>
> Masahiro Sakamoto
> Yah
+1
On Mon, Dec 6, 2021 at 4:51 AM Shivji Kumar Jha wrote:
> +1
>
> Regards,
> Shivji Kumar Jha
> http://www.shivjijha.com/
> +91 8884075512
>
>
> On Fri, 3 Dec 2021 at 08:46, Li Li wrote:
>
> > +1
> >
> > Thanks,
> > LiLi
> >
> > > On Dec 1, 2021, at 2:26 PM, Hang Chen wrote:
> > >
> > > +1
>
Welcome Dave!
- Sijie
On Sun, Dec 5, 2021 at 4:49 PM Huanli Meng wrote:
> Welcome Dave.
>
> BR//Huanli
>
> On Dec 6, 2021, at 8:46 AM, PengHui Li wrote:
>
> Welcome, Dave.
>
> Regards,
> Penghui
>
> On Sat, Dec 4, 2021 at 8:36 PM Dianjin Wang <
> djw...@streamnative.io.invalid> wrote:
>
>> Wel
Agree with Matteo.
+1 on this proposal.
On Tue, Dec 7, 2021 at 4:51 PM Matteo Merli wrote:
> I'm +1 on this proposal.
>
> > It looks interesting, but I see a major problem with this approach.
> > Basically we would be adding a way to tweak everything in Pulsar, from
> > Connections to what we a
I don't think you need a separate connector.
An identity function should be able to do the job for you.
- Sijie
On Mon, Nov 15, 2021 at 3:34 PM Neng Lu wrote:
> Just did a quick search, it's interesting we don't have a pulsar connector
> to move data among pulsar clusters.
> I guess people usu
I think we should have a PIP for this. Because this impacts all the
developers who are making documentation changes.
- Sijie
On Tue, Nov 16, 2021 at 8:46 AM Dave Fisher wrote:
> Hi -
>
> There are two efforts happening in the community around website refresh.
>
> (1) Docusaurus upgrades.
> (2)
+1
On Wed, Oct 27, 2021 at 7:10 AM Hang Chen wrote:
> +1
>
> Thanks,
> Hang
>
> Michael Marshall 于2021年10月27日周三 下午9:41写道：
> >
> > +1
> >
> > Michael
> >
> > > On Oct 27, 2021, at 7:40 AM, ranxiaolong...@gmail.com wrote:
> > >
> > > LGTM +1
> > >
> > > --
> > > Thanks
> > > Xiaolong Ran
> > >
>
Hi Vijaya,
Can you report the issue in the Flink Jira? We will follow up on the memory
leak issue.
The source connector was released as part of Flink 1.14 is a new
implementation based on the new Flink source API. If you are using Flink
1.12 or older versions, you can use this connector (
https:/
Thanks Masahiro!
- Sijie
On Tue, Oct 19, 2021 at 4:34 AM Masahiro Sakamoto
wrote:
> The Apache Pulsar team is proud to announce Apache Pulsar Node.js client
> version 1.3.2 and 1.4.1.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides si
+1 binding
On Thu, Sep 30, 2021 at 10:54 AM Matteo Merli wrote:
> 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.
> >
> > The iss
+1 binding
On Thu, Sep 30, 2021 at 2:06 AM PengHui Li wrote:
> +1 (binding)
>
> Thanks for the great work.
>
> Penghui
>
> On Thu, Sep 30, 2021 at 12:38 PM Enrico Olivelli
> wrote:
>
> > +1 (binding)
> >
> > Enrico
> >
> > Il Gio 30 Set 2021, 06:08 Yunze Xu ha
> > scritto:
> >
> > > Hi folks,
Hi Melissa,
Thank you for your efforts for putting this together!
I have a few comments:
1) Adding "vote" in the email title is a bit confusing. The design should
be brought up for discussion before going into a vote process.
2) The discussion (or "vote") should happen in the mailing list rather
ry high levels), and so for them it is harder to write super
> > efficient and high quality plugins using non-Java languages.
> >
> > So I see a huge value in adding this ability to the Pulsar Proxy.
> >
> > The only alternative to this PIP is to create a new f
sar's semantics should be maintained and distributed
> with Pulsar to provide the least friction possible.
>
> In particular, DataStax has seen a lot of interest in our Fast JMS
> implementation https://github.com/datastax/pulsar-jms and we would like to
> donate it to Apache Pul
> > > we absolutely need an adapter then we can use a pulsar-adapter gitrepo
> > and
> > > we should evaluate the feasibility of maintaining such adapters with
> > their
> > > different versions and their interest in the community. Thanks,Rajan*
> > &g
On Fri, Sep 3, 2021 at 5:07 AM Enrico Olivelli wrote:
> 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 protocol
> hand
Lari,
Thank you for bringing this up!
In general, I would love to see this being accepted to the project.
However, in the past, there were other language clients contributed to the
project. They were not accepted because the PMC doesn't have enough
bandwidth to staff it.
https://github.com/apach
I would like to see the clarification between the broker protocol handlers
and proxy protocol handlers before moving it to a vote thread.
I can see how it will cause confusion for protocol developers.
Yunze brought a good idea on KoP. But I don't think that's the right
direction. If you can give
mmunity are the Apache Pulsar PMC.
As such, the claim to represent the "Apache Pulsar Community" is only
one that can be made by the PMC.
Details:
https://lists.apache.org/thread.html/rba409e3b12067a2e69855ca57ced3fafe20bbeadedeb0441fe7d40c7%40%3Ctrademarks.apache.org%3E
On Thu, Aug 19,
Partick,
I am not a legal expert to answer the trademark question. I will consult
the trademarks team for this.
However, it is the PMC's responsibility to oversee the usage of "Apache
Pulsar" that follows the ASF policy.
- Sijie
On Thu, Aug 19, 2021 at 5:23 PM Patrick McFadin wrote:
> "Apach
on this point, it's perfectly
> > normal for PMC discussions around new proposals with decision-making
> > authority by the PMC to take place on the public dev list. The private
> > list is only necessary when confidentiality is required, and the dev list
> > allows no
+1 for standardizing the PIP workflow!
The proposal looks good!
- Sijie
On Wed, Aug 18, 2021 at 10:46 PM Matteo Merli wrote:
> This is a proposal that I promised to send out for a long time.
> It should be considered as a draft and I'd love to hear feedback on this.
>
> The motivations to impr
Sorry for the typo:
"isn't violating the ASF policy" -> "is violating the ASF policy"
On Wed, Aug 18, 2021 at 10:46 PM Sijie Guo wrote:
> Moving dev@ to BCC. I believe the following two major issues should be
> discussed and addressed in the original email th
Moving dev@ to BCC. I believe the following two major issues should be
discussed and addressed in the original email thread with PMC.
1) Creating sub-committees composed of vendor representatives isn't
violating the ASF policy. This PMC has expressed concerns when the original
proposal was raised.
I don't think we should create any sub-committees to bypass the PMC.
The sub-committee topic or proposal should be properly discussed and
approved by the PMC.
In regards to meetups, I don't think we should put every Pulsar meetup
under one umbrella group even this group is managed by PMC. Pulsar
m
You can follow the progress at https://github.com/trinodb/trino/pull/8020.
The original code doesn't conform to TrinoDB's standard. Marvin is
actively following up on that.
Our goal is still to get this completed as part of the 2.9 release.
- Sijie
On Fri, Aug 13, 2021 at 2:04 AM Enrico Olivell
Rayees,
It should work depending on how are you going to use the service mesh.
For example, in KOP (Kafka-on-Pulsar), we use istio to expose Kafka
service outside of Kubernetes' network.
You can also use Istio to eliminate the need for a Pulsar proxy as well.
If you can clarify a bit on what yo
Congrats Lin Lin! Well deserved!
- Sijie
On Mon, Aug 2, 2021 at 8:51 AM PengHui Li wrote:
>
> Hi everyone,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Lin Lin
> (https://github.com/315157973) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
Congrats Enrico! Well deserved!
- Sijie
On Mon, Aug 2, 2021 at 8:46 AM PengHui Li wrote:
>
> Congrats Enrico and thanks for the awesome contribution to the project.
>
> Regards,
> Penghui
>
> On Mon, Aug 2, 2021 at 10:52 PM Shivji Kumar Jha wrote:
>
> > Congrats Enrico. Been a huge follower of
Xiaolong - Congratulations!
Thanks to every contributor for making this happen!
- Sijie
On Sun, Jul 25, 2021 at 10:56 PM Dianjin Wang wrote:
>
> Congratulations!
>
> Best,
> Dianjin Wang
>
>
> On Mon, Jul 26, 2021 at 11:02 AM r...@apache.org
> wrote:
>>
>> The Apache Pulsar team is proud to a
+1
On Sat, Jul 24, 2021 at 7:29 AM Hang Chen 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.0. We have a lot of fixes already merged. So
> I would like to start to prepare our next patch release in the next few
>
Here are my two cents.
It is great to have more protocol handlers. I'd encourage people to
maintain the protocol handler themselves rather than pushing to the
upstream.
1. It is very hard for the community to maintain all protocol handlers
upstream and keep them updated. Similar situations happen
Yu,
Do you want to submit PRs to update those pages?
- Sijie
On Mon, Jul 26, 2021 at 12:34 AM Anonymitaet _ wrote:
>
> Hi all,
>
> Great idea.
>
> For the "contact" page, we can add "Pulsar community meeting info"
> (https://github.com/apache/pulsar/wiki/Community-Meetings) there as well.
>
>
apache-pulsar would be preferred.
On Fri, Jul 23, 2021 at 3:54 PM Chris Latimer
wrote:
>
> I've also noticed that most Pulsar-related questions on StackOverflow are
> tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want to
> recommend one tag over the other?
>
> On Fri, Jul 23, 2021
Hi Linlin,
Thank you for bringing this proposal to the community!
Since you are a committer, you should be able to create a wiki page on
Pulsar wiki. Can you do that?
- Sijie
On Tue, Jul 27, 2021 at 9:03 PM linlin wrote:
>
> Hi, All
>
> I have prepared a PIP for the Topic policy across multipl
Aaron,
That is a very valuable point. +1
Just FYI, we have been encouraging people to ask questions in
StackOverflow. But it doesn't work out well.
- Sijie
On Fri, Jul 23, 2021 at 9:49 AM Aaron Williams
wrote:
>
> Hello Apache Pulsar Community,
>
> Many of us community members were having a c
, "Anonymitaet _" wrote:
> > >
> > > Hi all,
> > >
> > > Thanks for the discussion.
> > >
> > > Before upgrading Docusaurus, we've collected some requirements from
> > > community and docum
Great finding!
Thanks Neng for fixing the issue!
- Sijie
On Thu, Jul 22, 2021 at 6:24 PM Neng Lu wrote:
>
> Hi All,
>
> I spent some time digging into the debezium connector integration test
> issue. And found that currently the connector's `ack()` method is a
> blocking call. This results in t
+1
- verified checksum
- run produce and consume
On Thu, Jul 22, 2021 at 11:59 PM PengHui Li wrote:
>
> +1
>
> - verified checksum
> - run produce and consume
>
> Thanks,
> Penghui
>
> On Thu, Jul 22, 2021 at 10:37 PM 丛搏 wrote:
>
> > +1
> >
> > Regards,
> > Bo
> >
> > r...@apache.org 于2021年7月2
+1
On Tue, Jul 20, 2021 at 4:16 AM PengHui Li wrote:
>
> +1
> On Jul 20, 2021, 7:24 AM +0800, Ming Luo ,
> wrote:
> > +1
> >
> > Thanks
> > Ming
> >
> > On Mon, 19 Jul 2021 at 18:55, Neng Lu wrote:
> >
> > > +1
> > >
> > > Neng Lu
> > >
> > > On 2021/07/19 08:44:11 "r...@apache.org" wrote:
> >
Penghui can probably help you there.
But I think it would be good to have CI jobs to publish those build images.
- Sijie
On Tue, Jul 20, 2021 at 1:18 AM Yunze Xu wrote:
>
> Hello,
> Currently Pulsar's CI workflows rely on some docker images, but I found these
> images are maintained mannually b
termine which container version is running and potentially
> update the container version on a per function basis.
Jerry - Thank you! That was what I meant.
>
> Best,
>
> Jerry
>
> On Mon, Jul 19, 2021 at 12:50 AM Enrico Olivelli
> wrote:
>
> > Sijie,
> > T
On Mon, Jul 19, 2021 at 12:50 AM Enrico Olivelli wrote:
>
> Sijie,
> Thank you for your feedback
> Some additional considerations inline
>
> Il Lun 19 Lug 2021, 06:47 Sijie Guo ha scritto:
>
> > I don't think this is a big problem. Because people can recompile
1 - 100 of 584 matches
Mail list logo
