Hi,
Though chunked messages are sequential for a specific producer, it's not
guaranteed that they will be contiguous when the broker receives them and
writes them to a ledger. So, it will be a little tricky to find out the
first message-id of any chunked-message at any given time unless broker
tag
The proposal should be https://github.com/apache/pulsar/issues/12129? I
think you can close this email thread to start a new one to avoid confusion.
Thanks,
Penghui
On Wed, Sep 22, 2021 at 2:31 PM 丛搏 wrote:
> Hello:
>
> We are sorry that there is an error in the existing transaction
> coordinat
Hi, Rajan.
I think we can make changes only on the client side. Probably only the part of
sendMessages of the producer.
When the producer sends a chunked message, the message-id of the first chunk
is stored temporarily in the producer until all chunks have been sent, and then
it is
returned
Hi Pulsar Community,
We found some problems in the transaction coordinator load mechanism.
For details, please see: https://github.com/apache/pulsar/issues/12129
Thanks.
Bo
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
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 with an equivalent from higher version JDK should
have no impact from functional
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:
osbornm commented on issue #122:
URL:
https://github.com/apache/pulsar-client-node/issues/122#issuecomment-924998580
@gaoran10 I can and have got the node client to build local after pulling
down the c++ library building and setting the ENV.
This is tangential to the problem I have
Hi Enrico,
This sounds like a useful feature. Do you expect to use it internally in
pulsar or should it be limited to external applications?
In thinking about authorization, what level of permission should be
required to create/update/delete these labels? It seems to me that these
should require
We already have a mechanism to store custom properties in managed
ledgers. So we don't need to store it separately.
--
Matteo Merli
On Wed, Sep 22, 2021 at 3:21 PM Michael Marshall wrote:
>
> Hi Enrico,
>
> This sounds like a useful feature. Do you expect to use it internally in
> pulsar or shou
I don't think pulsar should increase its dependency on ZK. Can we store it
somewhere else?
On Wed, Sep 22, 2021, 3:30 PM Matteo Merli wrote:
> We already have a mechanism to store custom properties in managed
> ledgers. So we don't need to store it separately.
> --
> Matteo Merli
>
>
> On Wed,
asagjj opened a new issue #422:
URL: https://github.com/apache/pulsar-manager/issues/422
Scene: pulsar with multiple adminhttpservers
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
Another option is to store the custom properties of the topic to the system
topic as the topic policy does.
The limitation is if using the system topic, we are not able to guarantee
the atomic operation for the topic creation and properties adding,
But it is required in some cases.
Yes, the manage
Congrats and thanks for the great work Hang.
Penghui
On Wed, Sep 22, 2021 at 8:42 PM Enrico Olivelli wrote:
> 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 r
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
16 matches
Mail list logo
