Hi Yubiao
I wonder what's the actual use case of mixing Exclusive-Mode and
Share-Mode of the same topic?
>From what I see, we should make clear the priority of Exclusive-Mode
and Share-Mode, and Exclusive > Share makes more sense to me.
Currently, depending on the time of which producer registere
Hi Haiting
> I wonder what's the actual use case of mixing Exclusive-Mode and
Share-Mode of the same topic?
I think there might be a scenario like this:
Users used multiple producers in shared mode before, but need to change to
exclusive producers later.
> From what I see, we should make clear t
Hi Yubiao:1. kick out all the connected Shared producers. This same as the mode
ExclusiveWithFencing, so the mode WaitForExclusive is no longer needed.I agree
this, but that doesn't mean we don't need `WaitForExclusive` . If there was a
producer of Exclusive before, WaitForExclusive still has t
Congrats!
Nicolò Boschi
Il giorno gio 10 nov 2022 alle ore 08:25 Aloys Zhang
ha scritto:
> Congratulations! tison
>
> Enrico Olivelli 于2022年11月10日周四 15:09写道：
>
> > Congratulations!
> >
> > Enrico
> >
> > Il Gio 10 Nov 2022, 08:07 Haiting Jiang ha
> > scritto:
> >
> > > Congratulations!
> > >
Hi all,
>From the previous discussion [1], we reached a consensus that
MessageId should only be a comparable and serializable opaque object
(only in Java client though). However, the APIs that return or accept
a MessageId have some hidden requirements.
Let's introduce the 5 implementations first
Hi Asaf,
> After reaching the end of the PIP I discovered a link to an issue that
> gives an example of a misconfiguration.
I’m sorry about this, currently, I’ve updated the PIP and added a link for the
`misconfigured` client.
> 1. Maybe we should put this code as a general wrapper for any comm
Tao,
I support the idea of tracking the same metric for all the possible commands.
One additional bonus would be to at least add a label with the
"tenant" or, even better, the "namespace".
This way in a multi-tenant system you can track down to the
user/application who is causing the load
Otherwis
Yunze,
great explanation, I support your proposals at 100%
Enrico
Il giorno gio 10 nov 2022 alle ore 13:17 Yunze Xu
ha scritto:
>
> Hi all,
>
> From the previous discussion [1], we reached a consensus that
> MessageId should only be a comparable and serializable opaque object
> (only in Java cli
One of the areas where Kafka has an advantage over Pulsar is around data
quality. Kafka conforms to the JSON Schema specification, which enables
integration with any technology that conforms to the standard, such as for
data validation, discoverability, lineage, versioning, etc.
Pulsar's implementa
Hi Michael,
> This PIP is similar to autorecovery throttling. I think the feature
> makes sense for the same reasons that throttling autorecovery makes
> sense.
Yes, the PIP’s key point is protect the broker, to prevent offloading takes too
much broker resources.
> Tangentially, can we decoup
Hi Enrico,
> One additional bonus would be to at least add a label with the
> "tenant" or, even better, the "namespace”.
I think this is a good idea, but there is a challenge: we reuse the Channel in
the client. Which means that some Consumers/Producers reuses a single Channel.
For ServerCnx
> Yes, the PIP’s key point is protect the broker, to prevent offloading takes
> too much broker resources.
Throttling also protects the bookkeeper. Reads that are used to
offload data are the lowest priority reads since they are not serving
an actual client. Since we don't have a way to tell book
GitHub user phijohns-tibco added a comment to the discussion: struggling with
pulsar functions in kubernetes
What version of Pulsar are you using?
I'm getting the same error with pulsar-admin. I'm not in kubernetes but bare
metal.
For me this only effects Pulsar 2.9.3. I had no problem with
Congratulations! tison
--
Thanks
Xiaolong Ran
Nicolò Boschi 于2022年11月10日周四 17:57写道：
> Congrats!
> Nicolò Boschi
>
>
> Il giorno gio 10 nov 2022 alle ore 08:25 Aloys Zhang <
> aloyszh...@apache.org>
> ha scritto:
>
> > Congratulations! tison
> >
> > Enrico Olivelli 于2022年11月10日周四 15:09写道：
> >
>
GitHub user tisonkun added a comment to the discussion: raspberry 3 -
pulsar-client python
Hi @anand-ftc! How did you try to compile it? With current information, I'd say
`pip3 install pulsar-client` should work.
cc @BewareMyPower
GitHub link:
https://github.com/apache/pulsar/discussions/1
GitHub user merlimat added a comment to the discussion: RoundRobinPartition
mode：enable batching and has key , What will be the run result?
If a key is provided on the message, that it will be honored. The round-robin
is only applied if there's no key.
You can find the logic in
https://githu
GitHub user anand-ftc added a comment to the discussion: raspberry 3 -
pulsar-client python
@tisonkun I tried first compiling the cpp shared objects following
https://github.com/apache/pulsar-client-cpp#compilation
Then followed the https://github.com/apache/pulsar-client-python to build the
GitHub user merlimat added a comment to the discussion: raspberry 3 -
pulsar-client python
@anand-ftc Which version of Python?
Can you post the result of `pip3 debug --verbose`?
GitHub link:
https://github.com/apache/pulsar/discussions/18423#discussioncomment-4114655
This is an automa
GitHub user merlimat added a comment to the discussion: raspberry 3 -
pulsar-client python
Oh, it's ARM32. We only have binaries for ARM64 so far.
GitHub link:
https://github.com/apache/pulsar/discussions/18423#discussioncomment-4114660
This is an automatically sent email for dev@pulsar
GitHub user anand-ftc added a comment to the discussion: raspberry 3 -
pulsar-client python
@merlimat pip3 debug returns error : unknown command "debug"
@merlimat yes you are correct .. its ARM32
GitHub link:
https://github.com/apache/pulsar/discussions/18423#discussioncomment-4114682
---
20 matches
Mail list logo
