"maxPropertiesSize" or "maxHeaderSize" in
> > > broker.conf and pass it to
> > > > client like maxMessageSize. But the implementation is much more
> > complex,
> > > and don't have the
> > > > benefit 2 and 3 mentioned in Motivation.
> > > >
> > > > ## Compatibility Issue
> > > > As a matter of fact, this PIP narrows down the sendable range.
> > > Previously, when maxMessageSize
> > > > is 1KB, it's ok to send message with 1KB properties and 1KB payload.
> > But
> > > with this PIP, the
> > > > sending will fail with InvalidMessageException.
> > > >
> > > > One conservative way is to add a boolean config
> > > "includeHeaderInSizeCheck" to enable this
> > > > feature. But I think it's OK to enable this directly as it's more
> > > reasonable, and I don't see good
> > > > migration plan if we add a config for this.
> > > >
> > > > [1] https://github.com/apache/pulsar/issues/13560
> > > >
> > > > Thanks,
> > > > Haiting Jiang
> > >
> > >
> > >
> > > --
> > > Zike Yang
> > >
> >
>
--
Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
gt; > > >>
> > > >> Dave Fisher 於 2022年1月4日 週二 06:06 寫道：
> > > >>
> > > >>> I don’t think we need a VOTE. Let’s do this by LAZY CONSENSUS.
> > > >>>
> > > >>>> On Jan 3, 2022, at 10:05 AM, Enrico Olivelli &g
ut
> > > > > >> we also don't want to clutter our repo with open PRs that won't
> > get
> > > > > merged.
> > > > > >>
> > > > > >> For example, I reviewed this PR [0] about 3 months ago. The
> > > > > >> contributor has not yet responded to my feedback and it doesn't
> > seem
> > > > > >> to fix an actual bug, so I think it is a candidate for closure.
> > Here
> > > > > >> is another example [1]. I closed this one because it had merge
> > > > > >> conflicts with a commit that fixed the same underlying issue.
> > > > > >>
> > > > > >> Note that our committer guidelines [2] do not provide guidance
> on
> > this
> > > > > >> subject.
> > > > > >>
> > > > > >> [0] - https://github.com/apache/pulsar/pull/11237
> > > > > >> [1] - https://github.com/apache/pulsar/pull/11162
> > > > > >> [2] - https://github.com/apache/pulsar/wiki/Committer-Guide
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Michael
> > > > > >>
> > > > >
> > > > >
> > > >
> > > > --
> > > > Jonathan Ellis
> > > > co-founder, http://www.datastax.com
> > > > @spyced
> >
>
>
> --
> Jonathan Ellis
> co-founder, http://www.datastax.com
> @spyced
>
--
Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
2021 at 11:23 PM Michael Marshall <
> >>>>>> mmarsh...@apache.org>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> +1 - thanks Enrico.
> >>>>>>>>>
> >>>>>>>>> - Michael
> >>>>>>>>>
> >>>>>>>>> On Sat, Dec 11, 2021 at 1:11 AM Lari Hotari
> >>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> +1
> >>>>>>>>>>
> >>>>>>>>>> la 11. jouluk. 2021 klo 9.07 Enrico Olivelli <
> >>>>> eolive...@gmail.com>
> >>>>>>>>>> kirjoitti:
> >>>>>>>>>>
> >>>>>>>>>>> Hello folks,
> >>>>>>>>>>> Yesterday we committed the release notes for 2.9.0.
> >>>>>>>>>>> I just have to publish a couple of other artifacts and update
> >>>>> the
> >>>>>>>> website
> >>>>>>>>>>> before announcing 2.9.0.
> >>>>>>>>>>> My plan is to complete the procedure next week.
> >>>>>>>>>>>
> >>>>>>>>>>> In the meantime, early next week, I believe it is time to
> >>>>> prepare
> >>>>>>>> the first
> >>>>>>>>>>> RC of 2.9.1, due to the log4j bug.
> >>>>>>>>>>>
> >>>>>>>>>>> If you are aware of problems on branch-2.9 or things to be
> >>>>>>>> cherry-picked
> >>>>>>>>>>> because they are blocker please let me know.
> >>>>>>>>>>>
> >>>>>>>>>>> Otherwise if branch-2.9 is stable I will cut the RC from what
> >>>>> we
> >>>>>>>> already
> >>>>>>>>>>> have now.
> >>>>>>>>>>>
> >>>>>>>>>>> I am volunteering as RM for 2.9.1 as I followed 2.9.0 and
> >>>>> release
> >>>>>>> is
> >>>>>>>>>>> basically non stable due to the bugs we discovered after
> >>>>>> completing
> >>>>>>>> the
> >>>>>>>>>>> VOTE and publishing the artifacts to dockerhub and Maven
> >>>>>>>>>>>
> >>>>>>>>>>> Best regards
> >>>>>>>>>>>
> >>>>>>>>>>> Enrico
> >>>>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
>
--
Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
; > > > >3.
> > > > > > >
> > > > > > >On Slack, we encourage them to post their question to Stack
> > > > Overflow
> > > > > > >
> > > > > > >
> > > > > > > Reasons:
> > > > > > >
> > > > > > >-
> > > > > > >
> > > > > > >We are on the free version of Slack and thus all
> > > questions/answers
> > > > > > >before the middle of June are lost (10k messages max).
> > > > > > >-
> > > > > > >
> > > > > > >We answer the same question over and over.
> > > > > > >-
> > > > > > >
> > > > > > > We want to make it easier for our community to find the
> > > > answers.
> > > > > > > -
> > > > > > >
> > > > > > >Developers expect answers to be on Stack Overflow
> > > > > > >-
> > > > > > >
> > > > > > >It is easier to copy and paste an error message into Google
> > and
> > > if
> > > > > it
> > > > > > >has been posted to Stack Overflow, then the questioner will
> > find
> > > > the
> > > > > > answer
> > > > > > >quickly.
> > > > > > >-
> > > > > > >
> > > > > > > Slack is not searchable by Google, plus we won’t lose the
> > > > > > > question/answer after 5 weeks
> > > > > > >
> > > > > > >
> > > > > > > Thoughts?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Aaron Williams
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
he Helm Chart, it would be better
> to have the ability to configure the transaction related services with
> specific options.
>
> What do you think ?
>
>
> Enrico
>
--
Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
ing else; we want to keep reinforcing whatever
they are looking at is worth spending a little more time step-by-step.
The nice thing is that you can roll this out section by section and still
get value from even the very first step.
--
Chris Herzog Messaging Engineering Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
e been released.
> So it is time for us to remove the CGO client from the main
> Apache Pulsar repo.
>
> If you have any ideas, please feel free to contact me.
>
> --
> Thanks
> Xiaolong Ran
>
>
>
--
Chris Herzog Messaging Team | O 630 300 7718 | M 815 263 3764 |
www.tibco.com
<http://www.tibco.com/>
