Hi Michael,
You are right, I already leave https://github.com/apache/pulsar/issues/8152.
Thanks,
Zixuan
Michael Marshall 于2023年2月15日周三 13:27写道：
> I added a review to https://github.com/apache/pulsar/pull/18336.
>
> I do not think it will be a problem to accept this PIP and to add OIDC
> suppor
Closed by 3 (binding), and 1(non-binding).
Thanks,
Zixuan
Michael Marshall 于2023年2月15日周三 13:31写道：
> +1 (binding)
>
> I have some comments on the PR that I'd like to discuss before it is
> merged, but I consider those minor implementation details.
>
> Thanks,
> Michael
>
> On Tue, Feb 14, 2023 a
Hi, All
First of all, I want to list all of the system topics as follows. That Yunze
has mentioned before.
Namespace level:
• pulsar/system
• transaction_coordinator_assign
• __transaction_log_
• resource-usage
• pulsar/
• healthcheck
Topic level:
• __change_events
• __transac
Hi Asaf
There is a link to introduce the dynamic configuration.
https://pulsar.apache.org/docs/2.10.x/admin-api-brokers/#dynamic-broker-configuration
Best,
Mattison
On Feb 14, 2023, 17:06 +0800, Asaf Mesika , wrote:
> On Tue, Feb 14, 2023 at 3:46 AM wrote:
>
> > Hi, Asaf
> >
> > Welcome to join
I have one question (apologies for the top posting).
The Broker (and the other Pulsar components) use the regular Pulsar
client to connect to "system topics"
and in general they use the Pulsar wire protocol.
The question is "how do you distinguish an internal component from a
user component ?"
Ho
Hi Enrico
I think it's a good question. We can introduce a new method in the
BrokerService to help brokers create the topic internally first(maybe just
metadata is enough), and then to use pulsar client connect to it.
WDYT?
Best,
Mattison
On Feb 16, 2023, 00:01 +0800, Enrico Olivelli , wrote:
Il giorno mer 15 feb 2023 alle ore 17:07 ha scritto:
>
> Hi Enrico
>
> I think it's a good question. We can introduce a new method in the
> BrokerService to help brokers create the topic internally first(maybe just
> metadata is enough), and then to use a pulsar client to connect to it.
I am so
Hi everyone! Enrico Olivelli asked me to repost it to the mailing list.
--- Me
I’m very worried that good answers from David Kjerrumgaard and others won’t be
googleable because it’s in Slack. To make any search you need to pay a monthly
subscription.
In my opinion, it would be wiser to make Sta
> I am sorry but I am not sure that this is enough to preventreads/writes from
> unallowed clients.
IMO, We can consider the authorisation part in another PIP because We are just
focusing on adding the topic name constraint of topic creation.
Maybe we can use another PIP to clearify all of syste
+100
Also note that for good or bad reasons, the number of questions on
StaOverflow is often used as a metric for the popularity of a project.
Le mer. 15 févr. 2023 à 13:12, Kiryl Valkovich
a écrit :
> Hi everyone! Enrico Olivelli asked me to repost it to the mailing list.
>
> --- Me
> I’m very
+1
Since web pages are more easily and public.
Best
Mattison
On Feb 16, 2023, 07:58 +0800, Christophe Bornet , wrote:
> +100
> Also note that for good or bad reasons, the number of questions on
> StaOverflow is often used as a metric for the popularity of a project.
>
> Le mer. 15 févr. 2023 à 13
Close this vote with 3 binding +1s votes:
* Matteo
* Bo
* Penghui
Thanks,
Yunze
On Wed, Feb 15, 2023 at 12:31 PM PengHui Li wrote:
>
> +1 binding
>
> The tests failed with curl 7.84. upgrading to 7.87 fixed the issue.
>
> Thanks,
> Penghui
>
> On Wed, Feb 15, 2023 at 10:36 AM 丛搏 wrote:
>
> > +
-1
Upgrading the client is harder than upgrading the broker. Pulsar
usually acts as a service to serve many lines of business and only a
single team is responsible to maintain the server side. It would be
hard to push all the client sides to upgrade the JDK.
Instead of upgrading the minimum requi
13 matches
Mail list logo
