Asaf,
Il Dom 4 Giu 2023, 15:37 Asaf Mesika ha scritto:
> Hi,
>
>
> Do we have a place we manage future Pulsar roadmap? Big ticket items,
> smaller ticket ones?
> I mean, I know we have GitHub issues, but that’s a forest.
> I was wondering if we have created a way to display those as a roadmap, o
Great news!
Thanks for sharing
Enrico
Il Ven 2 Giu 2023, 05:09 tison ha scritto:
> Thanks for sharing this information! Looking forward to the event :D
>
> Best,
> tison.
>
>
> Nozomi Kurihara 于2023年6月2日周五 11:04写道：
>
>> Dear Pulsar Enthusiasts,
>>
>> We are thrilled to announce the upcoming A
Il Mer 14 Giu 2023, 04:33 Rajan Dhabalia ha scritto:
> Hi,
>
> Are we proposing a change to break existing metrics compatibility
> (prometheus)? If that is the case then it's a big red flag as it will be a
> pain for any company to upgrade Pulsar as monitoring is THE most important
> part of the
> Hi,
>
> Are we proposing a change to break existing metrics compatibility
> (prometheus)? If that is the case then it's a big red flag as it will be a
> pain for any company to upgrade Pulsar as monitoring is THE most important
> part of the system and we don't even want to break compatibility fo
+1 to this change.
> I am not sure enabling hostname verification > by default is a good idea
> because it will cause deployment failures for > many users. Hostname
> verification requires x509 cert changes and wildcard SNName in some cases
> and it's not easy when broker hostname patterns don't
In my proposal, I do suggest deleting the existing metric system. You still
have the same Prometheus /metrics endpoint exposing metrics exactly as you
have today.
I plan to add an additional metric system based on OTel.
You will be able to consume via its native exporters;
1. Prometheus - there wil
On Wed, Jun 14, 2023 at 11:28 AM Enrico Olivelli
wrote:
> Il Mer 14 Giu 2023, 04:33 Rajan Dhabalia ha
> scritto:
>
> > Hi,
> >
> > Are we proposing a change to break existing metrics compatibility
> > (prometheus)? If that is the case then it's a big red flag as it will be
> a
> > pain for any c
Thanks for the details, Devin. Curios - 'We' stands for which company?
Can you take a look at my previous response to see if it answers the
concern you raised?
Thanks!
On Wed, Jun 14, 2023 at 1:49 PM Devin Bost wrote:
> > Hi,
> >
> > Are we proposing a change to break existing metrics compati
Fully understand.
How about a roadmap that primarily conveys general plans we see and agree
upon as a community?
Of course, it wouldn't contain any dates (not even years).
Maybe we can use that to reflect the "half-ness" / progress bar of certain
features that were left unfinished?
Here's an exa
There is no better place to surface various “To dos” than in an email thread
with an optional link to a GitHub issue or discussion. Any other place might be
hard to find in future years.
Best,
Dave
Sent from my iPhone
> On Jun 14, 2023, at 8:11 AM, Asaf Mesika wrote:
>
> Fully understand.
>
dependabot[bot] opened a new pull request, #8:
URL: https://github.com/apache/pulsar-presto/pull/8
Bumps [guava](https://github.com/google/guava) from 25.1-jre to 32.0.0-jre.
Release notes
Sourced from https://github.com/google/guava/releases";>guava's releases.
32.0.0
Mav
> Thanks for the details, Devin. Curios - 'We' stands for which company?
What do you mean? I was quoting Rajan when I said, "we."
Devin G. Bost
On Wed, Jun 14, 2023 at 10:02 AM Asaf Mesika wrote:
> Thanks for the details, Devin. Curios - 'We' stands for which company?
>
> Can you take a look
12 matches
Mail list logo
