t; >>>>
> >>>> --
> >>>> Thanks
> >>>> Xiaolong Ran
> >>>>
> >>>> Michael Marshall 于2023年2月8日周三 12:22写道：
> >>>>
> >>>> +1 (binding)
> >>>>
> >>>>
> >>>> Thanks,
; The only note I want to add is to make sure the PulsarAdmin access in
> >> Source and Sink is also controlled by the flag
> >> `exposePulsarAdminClientEnabled`. Similar to the following:
> >>
> >>
> >>
> https://github.com/apache/pulsar/blob/master/pulsar-funct
Now that the DISCUSSION thread has received some more input and some time
has passed I would like to start the VOTE again.
Best,
Alexander
On Tue, Jan 17, 2023 at 3:21 AM Bonan Hou
wrote:
> +1
>
> Bonan Hou
>
> On Mon, Jan 16, 2023 at 9:56 PM Alexander Preuss
> wrote:
Tue, Jan 3, 2023 at 10:32 PM Alexander Preuss
> wrote:
>
> > Hi all,
> >
> > I opened a PIP to discuss making PulsarAdmin accessible in Pulsar IO
> > connectors through SinkContext and SourceContext:
> > https://github.com/apache/pulsar/issues/19123
> >
> > Looking forward to hearing your thoughts,
> > Alex
> >
>
Hi Nicolò,
Thanks for driving this topic! I think it is a really good idea to improve
the distribution.
I had a read through the GH issue and I agree, that having the shell
available through homebrew would be nice.
Best,
Alexander
On Wed, Jan 18, 2023 at 11:11 AM Nicolò Boschi wrote:
> Hi
Hi everyone,
I'm starting the VOTE for PIP-237: Make PulsarAdmin accessible in
SinkContext and SourceContext: https://github.com/apache/pulsar/issues/19123
Discussion thread:
https://lists.apache.org/thread/b8r6b4p87qzfgfwmqfql7mqx8kmgorxg
I'd like to go ahead with implementing option B
Hi all,
I opened a PIP to discuss making PulsarAdmin accessible in Pulsar IO
connectors through SinkContext and SourceContext:
https://github.com/apache/pulsar/issues/19123
Looking forward to hearing your thoughts,
Alex
+1 non-binding
On Tue, Oct 18, 2022 at 12:49 PM Niclas Hedhman wrote:
>
> +1 non-binding
>
> Niclas
>
> On 2022-10-13 19:34, Christophe Bornet wrote:
> > Hi folks,
> >
> > I'd like to start a vote for the PIP-208: HTTP Sink (
> > https://github.com/apache/pulsar/issues/17719)
> >
> > The
Hi Christophe,
I think this is a very good idea!
I agree with Enrico that the body should depend on the record schema, but
it could also be done as a follow-up task.
Another thing to think about could be an optional batching mechanism that
would take a batch of records and send them as a list
+1
Having a reactive client for Pulsar would be very useful and would
strengthen Pulsar as a project going forward.
Best,
Alexander
On Tue, Aug 30, 2022 at 9:42 AM Enrico Olivelli wrote:
> I support the initiative, especially because I guess we will need someday
> to build a new native Java
ema works for instance.
>
> I don't think it is possible to support such API in the general case.
>
> If you want to use it as a key in a map then I suggest you to create a
> wrapper in your code.
>
>
> Enrico
>
> Il Ven 5 Ago 2022, 14:34 Alexander Preuss
> ha scritt
Hi together,
Thank you for driving this topic!
I agree that our customized convention is better than the Angular one.
+1 on the customized one
Best,
Alex
On Thu, Aug 11, 2022 at 11:02 AM Yu wrote:
> Hi team,
>
> For PIP 198: Standardize PR Naming Convention using GitHub Actions [1], we've
Hi Michael,
Thank you for bringing up this topic.
I was just running into an issue that prevented me from using the standard
Pulsar image in Testcontainers and found this discussion.
In my opinion, refactoring the docker builds to allow us to use the ASF
infra is a great idea.
I'm also looping
Hello Pulsar community,
I would like to start a discussion about PIP 197: Add Schema hash and
equals to public API.
You can find the proposal at https://github.com/apache/pulsar/issues/16959
as well as pasted below.
Looking forward to hearing your thoughts,
Alex
## Motivation
Currently, the
14 matches
Mail list logo
