Re: [ANNOUNCE] New Committer: Lin Chen

[Enrico Olivelli]

Congratulations

Enrico

Il Lun 14 Nov 2022, 07:30 Qiang Huang  ha
scritto:

> Congratulations!
>
> houxiaoyu  于2022年11月14日周一 13:40写道：
>
> > Congrats!
> >
> > Best,
> > Xiaoyu Hou
> >
> > PengHui Li  于2022年11月14日周一 12:28写道：
> >
> > > The Project Management Committee (PMC) for Apache Pulsar has invited
> > > Lin Chen (https://github.com/lordcheng10)
> > > to become a committer and we are pleased to announce that he has
> > accepted.
> > >
> > > Being a committer enables easier contribution to the
> > > project since there is no need to go via the patch
> > > submission process. This should enable better productivity.
> > >
> > > Welcome and congratulations, Lin Chen!
> > >
> > > Please join us in congratulating and welcoming Lin Chen onboard!
> > >
> > > Best Regards,
> > > Penghui on behalf of the Pulsar PMC
> > >
> >
>
>
> --
> BR,
> Qiang Huang
>

Re: [ANNOUNCE] New Committer: Zili Chen

[Qiang Huang]

Congratulations!

Zike Yang  于2022年11月14日周一 13:45写道：

> Hi, tison,
>
> Congratulations and welcome!
>
> BR,
> Zike Yang
>
> On Mon, Nov 14, 2022 at 12:58 PM Kai Wang 
> wrote:
> >
> > Congratulations! tison
> >
> > Thanks,
> > Kai
> > On Nov 10, 2022 at 8:16 AM +0800, dev@pulsar.apache.org, wrote:
> > >
> > > Congratulations! tison
>


-- 
BR,
Qiang Huang

Re: [ANNOUNCE] New Committer: Lin Chen

[Qiang Huang]

Congratulations!

houxiaoyu  于2022年11月14日周一 13:40写道：

> Congrats!
>
> Best,
> Xiaoyu Hou
>
> PengHui Li  于2022年11月14日周一 12:28写道：
>
> > The Project Management Committee (PMC) for Apache Pulsar has invited
> > Lin Chen (https://github.com/lordcheng10)
> > to become a committer and we are pleased to announce that he has
> accepted.
> >
> > Being a committer enables easier contribution to the
> > project since there is no need to go via the patch
> > submission process. This should enable better productivity.
> >
> > Welcome and congratulations, Lin Chen!
> >
> > Please join us in congratulating and welcoming Lin Chen onboard!
> >
> > Best Regards,
> > Penghui on behalf of the Pulsar PMC
> >
>


-- 
BR,
Qiang Huang

Re: [ANNOUNCE] New Committer: Zili Chen

[Zike Yang]

Hi, tison,

Congratulations and welcome!

BR,
Zike Yang

On Mon, Nov 14, 2022 at 12:58 PM Kai Wang  wrote:
>
> Congratulations! tison
>
> Thanks,
> Kai
> On Nov 10, 2022 at 8:16 AM +0800, dev@pulsar.apache.org, wrote:
> >
> > Congratulations! tison

Re: [ANNOUNCE] New Committer: Lin Chen

[houxiaoyu]

Congrats!

Best,
Xiaoyu Hou

PengHui Li  于2022年11月14日周一 12:28写道：

> The Project Management Committee (PMC) for Apache Pulsar has invited
> Lin Chen (https://github.com/lordcheng10)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> Welcome and congratulations, Lin Chen!
>
> Please join us in congratulating and welcoming Lin Chen onboard!
>
> Best Regards,
> Penghui on behalf of the Pulsar PMC
>

Re: [ANNOUNCE] New Committer: Lin Chen

[Max Xu]

Congratulations! Lin

Best,
Max Xu


On Mon, Nov 14, 2022 at 12:28 PM PengHui Li  wrote:

> The Project Management Committee (PMC) for Apache Pulsar has invited
> Lin Chen (https://github.com/lordcheng10)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> Welcome and congratulations, Lin Chen!
>
> Please join us in congratulating and welcoming Lin Chen onboard!
>
> Best Regards,
> Penghui on behalf of the Pulsar PMC
>

Re: [DISCUSSION] Support seek and ack multiple MessageIds

[Yunze Xu]

Hi Bo,

It makes sense to me. I will write the demo this week.

Thanks,
Yunze

Re: [ANNOUNCE] New Committer: Lin Chen

[Kai Wang]

Congrats!

Thanks,
Kai

Re: [ANNOUNCE] New Committer: Zili Chen

[Kai Wang]

Congratulations! tison

Thanks,
Kai
On Nov 10, 2022 at 8:16 AM +0800, dev@pulsar.apache.org, wrote:
>
> Congratulations! tison

Re: [DISCUSS] PIP-221: Make TableView support read the non-persistent topic

[Kai Wang]

Hi, pulsar-dev community,

Since the non-persistent topic support doesn't require API changes. I have 
pushed a PR to implement it, which has already been merged. 

See: https://github.com/apache/pulsar/pull/18375

And this PIP title has been changed to `Make TableView support TTL`.

PIP link: https://github.com/apache/pulsar/issues/18229

Thanks,
Kai

On 2022/11/04 02:28:41 Kai Wang wrote:
> Hi, pulsar-dev community,
> 
> I’ve opened a PIP to discuss : PIP-221: Make TableView support read the 
> non-persistent topic.
> 
> PIP link: https://github.com/apache/pulsar/issues/18229
> 
> Thanks,
> Kai
> 

Re: [ANNOUNCE] New Committer: Zili Chen

[tison]

Thank you! I'm glad to work with you talents :)

Best,
tison.


r...@apache.org  于2022年11月11日周五 10:48写道：

> Congratulations! tison
>
> --
> Thanks
> Xiaolong Ran
>
> Nicolò Boschi  于2022年11月10日周四 17:57写道：
>
> > Congrats!
> > Nicolò Boschi
> >
> >
> > Il giorno gio 10 nov 2022 alle ore 08:25 Aloys Zhang <
> > aloyszh...@apache.org>
> > ha scritto:
> >
> > > Congratulations! tison
> > >
> > > Enrico Olivelli  于2022年11月10日周四 15:09写道：
> > >
> > > > Congratulations!
> > > >
> > > > Enrico
> > > >
> > > > Il Gio 10 Nov 2022, 08:07 Haiting Jiang  ha
> > > > scritto:
> > > >
> > > > > Congratulations!
> > > > >
> > > > >
> > > > > BR,
> > > > > Haiting
> > > > >
> > > > > On Thu, Nov 10, 2022 at 2:14 PM Jun Ma 
> > wrote:
> > > > > >
> > > > > > Congratulations!
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Yu  ：
> > > > > > >
> > > > > > > > The Project Management Committee (PMC) for Apache Pulsar has
> > > > invited
> > > > > Zili
> > > > > > > > Chen (https://github.com/tisonkun)
> > > > > > > > to become a committer and we are pleased to announce that he
> > has
> > > > > > > accepted.
> > > > > > > >
> > > > > > > > Being a committer enables easier contribution to the
> > > > > > > > project since there is no need to go via the patch
> > > > > > > > submission process. This should enable better productivity.
> > > > > > > >
> > > > > > > > Welcome and congratulations, Zili Chen!
> > > > > > > >
> > > > > > > > Please join us in congratulating and welcoming Zili Chen
> > onboard!
> > > > > > > >
> > > > > > > > Best Regards,
> > > > > > > > Yu on behalf of the Pulsar PMC
> > > > > > > >
> > > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Committer: Lin Chen

[tison]

Congrats!

Best,
tison.


PengHui Li  于2022年11月14日周一 12:28写道：

> The Project Management Committee (PMC) for Apache Pulsar has invited
> Lin Chen (https://github.com/lordcheng10)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> Welcome and congratulations, Lin Chen!
>
> Please join us in congratulating and welcoming Lin Chen onboard!
>
> Best Regards,
> Penghui on behalf of the Pulsar PMC
>

[ANNOUNCE] New Committer: Lin Chen

[PengHui Li]

The Project Management Committee (PMC) for Apache Pulsar has invited
Lin Chen (https://github.com/lordcheng10)
to become a committer and we are pleased to announce that he has accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

Welcome and congratulations, Lin Chen!

Please join us in congratulating and welcoming Lin Chen onboard!

Best Regards,
Penghui on behalf of the Pulsar PMC

Re: [DISCUSSION] Redesign the MessageId interface

[PengHui Li]

Great discussion!
I agree with the conclusions!

IMO, we should not encourage users to touch the different implementations
of the MessageId.
Instead, we should provide a `MesssageIdUtils` in the client library(not
the interface)
with annotations `@InterfaceAudience.Public @InterfaceStability.Stable`. It
is just for
the specific purpose that users have to access the LedgerId and EntryId.

Thanks,
Penghui

On Sat, Nov 12, 2022 at 6:53 AM Michael Marshall 
wrote:

> Great discussion. I generally agree with the conclusions.
>
> I'll add two points.
>
> Several endpoints in the topics admin api require that message ids are
> consistently serialized and deserialized over HTTP. For example, the
> reset cursor call requires a message id in a correct format or
> "latest" or "earliest". I don't think this is a break in the
> abstraction, but it does imply that the serialization definitions
> (e.g. `toString()`) in each client language need to be consistent.
>
> Second, the admin api exposes the ledgerId/entryId implementation with
> the get message id endpoint, which asks users to specify a ledger id
> and an entry id instead of a serialized message id:
>
>
> https://github.com/apache/pulsar/blob/681d51d54937becc5c436cece3b731150afdf6d1/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/v2/PersistentTopics.java#L1930-L1944
>
> The Admin Client exposes this endpoint here:
>
>
> https://github.com/apache/pulsar/blob/82237d3684fe506bcb6426b3b23f413422e6e4fb/pulsar-client-admin-api/src/main/java/org/apache/pulsar/client/admin/Topics.java#L1658-L1682
>
> Based on the conclusion of this thread, it seems like we should
> deprecate the affected methods and replace them with ones that take a
> message id instead.
>
> Thanks,
> Michael
>
>
>
> On Wed, Nov 9, 2022 at 8:34 PM Yunze Xu 
> wrote:
> >
> > I also changed my mind after I saw Flink's MesssageIdUtils
> implementation.
> >
> > Now it's clear to me that:
> > - For application users, the APIs in the pulsar-client-api module are
> > what they should use.
> > - For Pulsar ecosystem developers, the APIs in the pulsar-client
> > module are interfaces
> >
> > So at the moment, these MessageId implementations could already be used
> in some
> > external applications.
> >
> > In conclusion,
> > 1. The MessageId interface should not be touched
> > 2. The public methods of the MessageId implementations should not be
> touched
> >
> > Based on these two key points, I'm going to look into these
> > implementations and mark
> > some as deprecated but they should still work like before.
> >
> > Thanks,
> > Yunze
> >
> > On Thu, Nov 10, 2022 at 3:50 AM Rajan Dhabalia 
> wrote:
> > >
> > > Hi,
> > >
> > > I was reading the email thread why we want to change MessageId
> interface:
> > > https://lists.apache.org/thread/rdkqnkohbmkjjs61hvoqplhhngr0b0sd
> > > >> Currently we have the following 5 implementations of MessageId:
> > > >> These implementations are such a mess. For example, when users get a
> > > MessageId from `Producer#send`:
> > >
> > > I think above discussion started by stating that MessageId has multiple
> > > implementations eg: MessageIdImpl, BatchMessageIdImpl,
> ChunkMessageIdImpl,
> > > etc.. and as a client we receive a single MessageId with send message
> API.
> > >
> > > Well, I see it's expected and very well defined behavior. No matter
> what
> > > implementation client library is internally using, as a user for my
> topic I
> > > should be able to publish and consume messages by providing specific
> > > configurations. The moment a user has to know implementation details
> of a
> > > client library such as chunk or batch message internals, there will be
> a
> > > strong dependency created between application and server implementation
> > > which is a RED flag for any system. Abstraction helps user adoption by
> > > simplifying user API and allowing systems to enhance without worrying
> about
> > > application dependency.
> > > Removing abstraction of MessageId and extracting implementation
> information
> > > in getter API will prevent us to make any implementation change (eg:
> won't
> > > be able to change chunk mesasgeId behavior which we might need in
> future
> > > for Shared-subscription), introduce hacks for any enhancement by making
> > > sure existing internal implementation can't change (eg: if we can't
> change
> > > chunk/batch-message-Id then we might create a new wrapper and attach to
> > > existing messageId which will make even things worse), and even
> prevent us
> > > to change backend implementation (eg: we will be stuck with BK-Ledger
> > > implementation forever).
> > > Pulsar is used for many large scale business usecaeses with a large
> number
> > > of users and it can create a nightmare for operators and users if we
> remove
> > > abstractions and start following the practice of exposing system
> internals
> > > to user applications.
> > >
> > > Thanks,
> > > Rajan
> > >
> > >
> > > On Tue, Nov 8, 2022 at 6:05 PM Yunze Xu 
> > > 

Re: [DISCUSSION] Support seek and ack multiple MessageIds

[丛搏]

Hi Yunze,

Yunze Xu  于2022年11月10日周四 20:17写道：

> ```java
> Map> seekAsync(Map
> messageIdMap);
> Map> acknowledgeAsync(Map MessageId> messageIdMap);
> Map>
> acknowledgeCumulativeAsync(Map messageIdMap);
> ```
why not add the method using `String topicName directly, MessageId
msgId` directly?
like:
```
CompletableFuture seekAsync(String topicName, MessageId msgId);
CompletableFuture acknowledgeAsync(String topicName, MessageId msgId);
CompletableFuture acknowledgeCumulativeAsync(String topicName,
MessageId msgId);
```
it is more simple and easy to understand. otherwise, we need to add the method
```
Map>>
acknowledgeAsync(Map> messageIdMap);
```

[GitHub] [pulsar] adrianog added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user adrianog added a comment to the discussion: Apache Beam support for 
Pulsar

Any update?

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131267


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] alexvanboxel added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user alexvanboxel added a comment to the discussion: Apache Beam support 
for Pulsar

I've taken over the ticket. I'm familiar with Beam, less so with Pulsar (I want 
to learn Pulsar, creating the IO). I'll be starting locally with Pulsar in 
standalone mode, as soon as I have a prototype I'll keep updates on this thread.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131263


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] chethanuk-plutoflume added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user chethanuk-plutoflume added a comment to the discussion: Apache Beam 
support for Pulsar

> Apache Beam -> Pulsar pipeline working

Cool, :)

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131266


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] alexvanboxel added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user alexvanboxel added a comment to the discussion: Apache Beam support 
for Pulsar

Great, I appreciate the help. I can happily report that after a few hours I 
already got some basic Google Cloud Pubsub -> Apache Beam -> Pulsar pipeline 
working (on the local runner). Don't get too excited to, still a lot of work to 
be done.

I'll have a look at the integrations.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131265


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] sijie added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user sijie added a comment to the discussion: Apache Beam support for 
Pulsar

@alexvanboxel awesome! much appreciated your help!

You can also check how Pulsar was integrated with Spark and Flink as a 
reference. The pulsar-flink one is the one is contributed to upstream Flink as 
[FLIP-72](https://cwiki.apache.org/confluence/display/FLINK/FLIP-72%3A+Introduce+Pulsar+Connector)
 and 

https://github.com/streamnative/pulsar-spark
https://github.com/streamnative/pulsar-flink

@yjshen can help answer any questions about such integrations.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131264


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] sijie added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user sijie added a comment to the discussion: Apache Beam support for 
Pulsar

@rfuerst87 - the beam community is doing the work. You can track the progress 
here - https://issues.apache.org/jira/browse/BEAM-8218

I will follow up there as well. 

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131261


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] svenhornberg added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user svenhornberg added a comment to the discussion: Apache Beam support 
for Pulsar

@sijie thank you for clarifying 

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131259


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] rfuerst87 added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user rfuerst87 added a comment to the discussion: Apache Beam support 
for Pulsar

Any updates on this matter? Would be interested in a Beam Connector too :)

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131260


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] rfuerst87 added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user rfuerst87 added a comment to the discussion: Apache Beam support 
for Pulsar

@sijie Thanks for the update. Thought you might have some more insights from 
the mailing list. Will follow the topic in JIRA.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131262


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] sijie added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user sijie added a comment to the discussion: Apache Beam support for 
Pulsar

@svenhornberg The beam community was trying to drive the development for this 
connector. Since they are the experts of beam. I didn't closely follow the 
progress there. Happy to follow up with them and get back here.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131258


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] sijie added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user sijie added a comment to the discussion: Apache Beam support for 
Pulsar

@svenhornberg there is a discussion in BEAM mailing list. We will collaborate 
with beam community on adding a pulsar connector in BEAM repo.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131256


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] svenhornberg added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user svenhornberg added a comment to the discussion: Apache Beam support 
for Pulsar

okay, looks like there is a story for that 
(https://issues.apache.org/jira/browse/BEAM-8218), but anyway it would be a 
push for pulsar. Maybe working together on this is an option.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131255


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] aahmed-se added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user aahmed-se added a comment to the discussion: Apache Beam support 
for Pulsar

this should be a request in the beam repo.

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131254


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] svenhornberg added a comment to the discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user svenhornberg added a comment to the discussion: Apache Beam support 
for Pulsar

Any statement if you would try to implement it ? 3 months have passed

GitHub link: 
https://github.com/apache/pulsar/discussions/18453#discussioncomment-4131257


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] svenhornberg created a discussion: Apache Beam support for Pulsar

[GitBox]

GitHub user svenhornberg created a discussion: Apache Beam support for Pulsar

I would like to use Apache Beam and Pulsar as my source, for writing my batch 
or streaming jobs. 

Please consider adding a PulsarIO class to the sdk like Kafka 
(https://beam.apache.org/releases/javadoc/2.4.0/org/apache/beam/sdk/io/kafka/KafkaIO.html)

I found the pulsar-flink and pulsar-spark folders, but i really like the Apache 
Beam API.
Maybe you could add a pulsar-beam example or subfolder



GitHub link: https://github.com/apache/pulsar/discussions/18453


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

Direct Approach for pulsar integration with spark

[Maneesh Bhunwal]

Hi Team,

There are 2 approaches to integrate apache kafka with apache spark as
mentioned here

with pros and cons.

But the current pulsar spark adaptor

only gives the option to integrate with a receiver based approach. This
makes migration from kafka to pulsar difficult as we are having to maintain
another intermediate store to make sure we don't lose any updates.


Are there any plans to work on the direct approach? Was it missed
intentionally? IF we have plans, I would like to contribute to it.


Regards
Maneesh Bhunwal

[GitHub] [pulsar] jesumyip edited a discussion: pulsar helm installation - deprecated api in local storage provisioner

[GitBox]

GitHub user jesumyip edited a discussion: pulsar helm installation - deprecated 
api in local storage provisioner

According to 
[https://pulsar.apache.org/docs/helm-deploy/#install-local-storage-provisioner](https://pulsar.apache.org/docs/helm-deploy/#install-local-storage-provisioner),
 we have to install this helm chart prior to installing the Pulsar one.

The local-storage-provisioner helm chart is using a deprecated API. I get this 
error when attempting to deploy it in GKE (v1.23.8-gke.1900):

` no matches for kind "DaemonSet" in version "extensions/v1beta1"`

Based on 
[https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/),
 I have to change the version from `extensions/v1beta1` to `api/v1`. Indeed, 
when I change the version, the helm chart installs correctly.

Can someone confirm this?

GitHub link: https://github.com/apache/pulsar/discussions/18448


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org

[GitHub] [pulsar] jesumyip edited a discussion: pulsar helm installation - deprecated api in local storage provisioner

[GitBox]

GitHub user jesumyip edited a discussion: pulsar helm installation - deprecated 
api in local storage provisioner

According to 
[https://pulsar.apache.org/docs/helm-deploy/#install-local-storage-provisioner](https://pulsar.apache.org/docs/helm-deploy/#install-local-storage-provisioner),
 we have to install this helm chart prior to installing the Pulsar one.

The local-storage-provisioner helm chart is using a deprecated API. I get this 
error when attempting to deploy it in GKE (v1.23.8-gke.1900):

` no matches for kind "DaemonSet" in version "extensions/v1beta1"`

Based on 
[https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/),
 I have to change the version from `extensions/v1beta1` to `api/v1`. Indeed 
when I change the version, the helm chart installs correctly.

Can someone confirm this?

GitHub link: https://github.com/apache/pulsar/discussions/18448


This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org