Hi Dave Fisher,
> There are some PRs that are coming in that must be included.
How's the progress on these PRs?
Best,
Mattison
On Wed, 25 May 2022 at 21:33, Just do it
wrote:
> +1
> Thanks,
> Dezhi
>
>
>
>
>
> -- Original --
> From: Hang Chen Date: Wed,May 25,
This is a good idea, but I have a concern, Pulsar has the config
`brokerMaxConnections` to control max connection count against one broker. If
the connection is closed, it will re-connect when consumers or producers start
to consume and produce messages again, but this time the max connection co
Dear Pulsar community,
I opened PIP-173 https://github.com/apache/pulsar/issues/15902 to create a
built-in Function implementing the most common basic transformations.
Let me know what you think.
Best regards,
Christophe
--
## Motivation
Currently, when users want to modify the data in P
> It should be reflected in the release notes somehow - don't know the
process for that.
Yes, we are using the label `release/important-notice` to track the
important things we need to highlight in the release not.
I have added the label.
I support the proposal.
Thanks,
Penghui
On Thu, Jun 2, 2
+1
Penghui
On Thu, Jun 2, 2022 at 8:21 PM guo jiwei wrote:
> +1
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Wed, Jun 1, 2022 at 3:12 PM Yubiao Feng
> wrote:
>
> > Hi Pulsar Community:
> >
> > There were some mistakes in the last email, so I have corrected them.
> >
> > I would like to start a VO
+1
Regards
Jiwei Guo (Tboy)
On Wed, Jun 1, 2022 at 3:12 PM Yubiao Feng
wrote:
> Hi Pulsar Community:
>
> There were some mistakes in the last email, so I have corrected them.
>
> I would like to start a VOTE on "Auto release client useless connections"
> (PIP-165).
>
> Proposal Link: [PIP-165
Dear Pulsar community members,
Here's a report of the flaky tests in Pulsar CI during the observation
period of 2022-05-26 to 2022-06-02 .
The full report is available as a Google Sheet,
https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit?usp=sharing
The repor
> Ok. I would add in the Compatability change another section with bold or
> capital letters to highlight you're creating a breaking change. It should
> be reflected in the release notes somehow - don't know the process for that.
Ok, I added to `Incompatible case`. PTAL.
Thanks,
Baodi Shi
> 202
>
> I tend to fail. Although this breaks the current logic. but the current
> implementation can be considered is a bug.
Ok. I would add in the Compatability change another section with bold or
capital letters to highlight you're creating a breaking change. It should
be reflected in the release no
