Congratulations! tison
Enrico Olivelli 于2022年11月10日周四 15:09写道：
> Congratulations!
>
> Enrico
>
> Il Gio 10 Nov 2022, 08:07 Haiting Jiang ha
> scritto:
>
> > Congratulations!
> >
> >
> > BR,
> > Haiting
> >
> > On Thu, Nov 10, 2022 at 2:14 PM Jun Ma wrote:
> > >
> > > Congratulations!
> > >
> >
Yubiao,
Il Gio 10 Nov 2022, 07:40 Yubiao Feng
ha scritto:
> Hi all,
>
> Now if an Exclusive-Mode producer has been registered, we can register
> another WaitForExclusive-Mode producer. When the old producer goes
> offline, the new producer will take over as the new exclusive producer.
>
> < Hig
Congratulations!
Enrico
Il Gio 10 Nov 2022, 08:07 Haiting Jiang ha scritto:
> Congratulations!
>
>
> BR,
> Haiting
>
> On Thu, Nov 10, 2022 at 2:14 PM Jun Ma wrote:
> >
> > Congratulations!
> >
> >
> > >
> > > Yu ：
> > >
> > > > The Project Management Committee (PMC) for Apache Pulsar has inv
Congratulations!
BR,
Haiting
On Thu, Nov 10, 2022 at 2:14 PM Jun Ma wrote:
>
> Congratulations!
>
>
> >
> > Yu ：
> >
> > > The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> > > Chen (https://github.com/tisonkun)
> > > to become a committer and we are pleased to announ
Hi all,
Now if an Exclusive-Mode producer has been registered, we can register
another WaitForExclusive-Mode producer. When the old producer goes
offline, the new producer will take over as the new exclusive producer.
< Highlight >But if some Shared-Mode producers have been registered, we can
re
GitHub user github-actions[bot] added a comment to the discussion: Pulsar Audit
- Question
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussions/18404#discussioncomment-4104450
This is an automatically sent email for dev@
Congratulations!
>
> Yu ：
>
> > The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> > Chen (https://github.com/tisonkun)
> > to become a committer and we are pleased to announce that he has
> accepted.
> >
> > Being a committer enables easier contribution to the
> > proje
Congratulations!
Thanks
ZhangJian He
On Thu, 10 Nov 2022 at 14:01, houxiaoyu wrote:
> Congratulations!
>
> Best,
> Xiaoyu Hou
>
> Yu 于2022年11月10日周四 08:16写道：
>
> > The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> > Chen (https://github.com/tisonkun)
> > to become a co
Hi Martijn,
Thanks for your help! We successfully integrate Matomo to the Pulsar
website now.
I'd like to know how to create an account to add segments or further
analysis board. It seems an Apache account is not carried to Matomo account
system.
Best,
tison.
tison 于2022年11月7日周一 16:49写道：
>
>
Congratulations!
Best,
Xiaoyu Hou
Yu 于2022年11月10日周四 08:16写道：
> The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> Chen (https://github.com/tisonkun)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a committer enables easier contrib
Congratulations to tisun kun / zilli chen!
Welcome!
Sent from my iPhone
> On Nov 9, 2022, at 4:16 PM, Yu wrote:
>
> The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> Chen (https://github.com/tisonkun)
> to become a committer and we are pleased to announce that he has
> Congratulations! Zili
> 在 2022年11月10日，上午11:18，Max Xu 写道：
>
> Congratulations! Zili
GitHub user BewareMyPower added a comment to the discussion: [QUESTION] Thread
safe problem about HandlerState#changeToReadyState
Is following implementation better?
```java
private static boolean notClosed(State state) {
return state == State.Uninitialized || state == State.Connec
GitHub user codelipenghui added a comment to the discussion: [QUESTION] Thread
safe problem about HandlerState#changeToReadyState
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussions/18401#discussioncomment-4103574
This
GitHub user BewareMyPower created a discussion: [QUESTION] Thread safe problem
about HandlerState#changeToReadyState
I'm not sure if it's bug. It's more a question. As we can see,
https://github.com/apache/pulsar/blob/608929227824fe4303f46aa432e42af77bcbf625/pulsar-client/src/main/java/org/apa
Congratulations! Zili
Best,
Max Xu
On Thu, Nov 10, 2022 at 8:16 AM Yu wrote:
> The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> Chen (https://github.com/tisonkun)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a committer enabl
I also changed my mind after I saw Flink's MesssageIdUtils implementation.
Now it's clear to me that:
- For application users, the APIs in the pulsar-client-api module are
what they should use.
- For Pulsar ecosystem developers, the APIs in the pulsar-client
module are interfaces
So at the moment
GitHub user blaghed added a comment to the discussion: Pulsar Operator On
Kubernetes
Hi all,
I'm very much interested in the discussion revolving around the Cluster and
Resource Operators for Pulsar.
So, kind of hope that the reason this ticket went quiet is that you moved the
ongoing convo o
GitHub user tisonkun added a comment to the discussion: Pulsar Operator On
Kubernetes
Open-ended discussion. Moved to the Discussions forum.
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103123
This is an automatically sent email for dev@pulsar.apach
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@nicknezis I‘ve invited you to join the channel
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103121
This is an automatically sent email for dev@pulsar.apache.org.
T
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@nicknezis Hi,
Sorry, I didn't know there was pulsar slack，now, I created one pulsar operator
channel in the Pulsar Slack，We will discuss the following here.
There's another team looking at the same thing, we
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@chrsoo OK
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103117
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email t
GitHub user nicknezis added a comment to the discussion: Pulsar Operator On
Kubernetes
Why not just an #operator channel in the Pulsar Slack? We hang out in there so
not sure if this is big enough effort to need a whole new Slack.
Having a design spec laid out is a great idea because we are s
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
I created slack https://pulsaroperator.slack.com/
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103118
This is an automatically sent email for dev@pulsar.apache.org.
GitHub user chrsoo added a comment to the discussion: Pulsar Operator On
Kubernetes
> @sijie yes, exactly. Should we take your comment regarding StreamNative to
> mean that you are planning to open source an Operator for Pulsar on
> Kubernetes that deals with the full scope of CRD's for Pulsa
GitHub user sijie added a comment to the discussion: Pulsar Operator On
Kubernetes
I think both ansible and go operators can co-exist. I would also recommend
submitting the operators to the operator hub as well so that it can be exposed
to wider community.
GitHub link:
https://github.com/ap
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
The next step is to publish to [OperatorHub](https://operatorhub.io/)
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103115
This is an automatically sent email for de
GitHub user chrsoo added a comment to the discussion: Pulsar Operator On
Kubernetes
@sijie yes, exactly. Should we take your comment regarding StreamNative to mean
that you are planning to open source an Operator for Pulsar on Kubernetes that
deals with the full scope of CRD's for Pulsar mana
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
Operator add pulsar manager component success.
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103112
This is an automatically sent email for dev@pulsar.apache.org.
To
GitHub user nicknezis added a comment to the discussion: Pulsar Operator On
Kubernetes
This is cool to see. A team I am on was going to start making a Pulsar
Operator using Ansible OperatorSDK.
https://github.com/operator-framework/operator-sdk/blob/master/doc/ansible/user-guide.md
Here is
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@chrsoo OK, Looking forward to you PR.
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103111
This is an automatically sent email for dev@pulsar.apache.org.
To unsubsc
GitHub user sijie added a comment to the discussion: Pulsar Operator On
Kubernetes
@chrsoo @sky-big @wolfstudy I think what @chrsoo request is an operator for the
full lifecycle management for all the resources within a Pulsar instance. This
includes both ClusterOperator and ResourceOperator.
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@chrsoo I generally understand what you mean, Starting with Tenants CRDs, Can
you make a specific design and let everyone discuss？
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussionco
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@wolfstudy @sijie @jiazhai Can you disscuss it together?
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103107
This is an automatically sent email for dev@pulsar.a
GitHub user chrsoo added a comment to the discussion: Pulsar Operator On
Kubernetes
@wolfstudy thanks for the tip (I am aware) but how is
[pulsar-manager](https://github.com/apache/pulsar-manager) not **imperative**?
A web UI where you do point-and-click is virtually the same thing as issuing
GitHub user wolfstudy added a comment to the discussion: Pulsar Operator On
Kubernetes
> I would really like to get out of an imperative approach based on
> pulsar-admin for managing the cluster.
@chrsoo Maybe the [pulsar-manager](https://github.com/apache/pulsar-manager) is
a good idea for
GitHub user chrsoo added a comment to the discussion: Pulsar Operator On
Kubernetes
The difficulty here is where to draw the line between more or less static
configuration and what should remain dynamically defined at runtime by the
clients/users of the system. This might vary in different co
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
@chrsoo Cloud you please give a sepcific example based on your sence? then we
can add this function in the pulsar operator.
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4
GitHub user chrsoo added a comment to the discussion: Pulsar Operator On
Kubernetes
Great initiative! I know you have to start somewhere and cannot do everything
at once but have you thought about CRD's for Sources and Sinks? What about
configuration like Channels, Tenants and Namespaces?
I
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
Next step concern pulsar stateful component(include Bookeeper and Zookeeper),
use operator control complex stateful component.
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncommen
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
Basically realized the function of pulsar operator，include pulsar dashboard,
grafana, prometheus and so on [Pulsar
Operator](https://github.com/sky-big/pulsar-operator)，weclome to use and
contribute.
GitHub
GitHub user sky-big added a comment to the discussion: Pulsar Operator On
Kubernetes
Welcome everyone to contribute
GitHub link:
https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103099
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, pl
GitHub user sky-big created a discussion: Pulsar Operator On Kubernetes
Add pulsar operator for kubernetes(https://github.com/sky-big/pulsar-operator)
based on deployment/kubernetes/*.yaml
GitHub link: https://github.com/apache/pulsar/discussions/18398
This is an automatically sent emai
The Project Management Committee (PMC) for Apache Pulsar has invited Zili
Chen (https://github.com/tisonkun)
to become a committer and we are pleased to announce that he has accepted.
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission
Hi,
I was reading the email thread why we want to change MessageId interface:
https://lists.apache.org/thread/rdkqnkohbmkjjs61hvoqplhhngr0b0sd
>> Currently we have the following 5 implementations of MessageId:
>> These implementations are such a mess. For example, when users get a
MessageId from `
FWIW, the Flink Pulsar connector hacky parses the message id internals to
get the next message id:
https://github.com/apache/flink/blob/421f057a7488fd64854a82424755f76b89561a0b/flink-connectors/flink-connector-pulsar/src/main/java/org/apache/flink/connector/pulsar/source/enumerator/cursor/MessageId
After reading Joe's comments I have changed my mind.
Actually it is better to not expose "ledgerId" and "entryId" to client
applications.
They are useless pieces of information.
And also if in the future we want to change the way we internally
address a message we will always have to support these
Hi Jiaqi,
> I don't think `tostring` should be used in any serious case because it has
no standard.
I agree. But it's better to keep it not changed. Just like my previous reply, it
might be a de-facto standard because the `toString()` like methods are used
in logging, not only for debugging. For
Hi Joe,
I think the most controversial point is what should a MessageId be used for.
>From your opinion, it should only be used as a comparable object (opaque),
which represents the position of a message [1]. What I have thought is,
MessageId should be a wrapper of the MessageIdData in PulsarApi.p
Thanks, this is very inspiring to me.
But I have a different opinion on `tostring`.
>>You can only see a representation from `toString` method and got some
output like "0:0:-1:0".
I don't think `tostring` should be used in any serious case because it has
no standard. There is no constraint on ho
Messageid is an identifier which identifies a message. How that id is
constructed, or what it contains should not matter to an application, and
an application should not assume anything about the implementation of that
id.
>What about the partition index? We have a `TopicMetadata` interface tha
Hi Haiting,
> But please make sure we have to make it compatible with previous
implementations, like the `toString` method
Yeah, I agree, I will keep it compatible.
BTW, while I'm working on this, I found the MessageId implementations
are more complicated than I thought. The MessageIdImpl class
Hi all,
What's status of this PIP?
There's an issue talking about fixable vulnerabilities in the latest release.
https://github.com/apache/pulsar/issues/18348
>From what I see, one of the problems is that we take too long to make a new
>release ( over 2 months for 2.10.2 ). Hopefully, this PIP
GitHub user Jason918 added a comment to the discussion: Why pulsar retention
quota must exceed configured backlog quota
> Hello @Jason918 , @michaeljmarshall , but I still confused, could you please
> explain for me why backlog quota couldn't exceed the retention? Is there any
> risk if we se
54 matches
Mail list logo
