Re: Discuss about creating partitioned topic in V1

> Having said that, V1 admin API was in effect considered as "soft deprecated" since Pulsar 2.0. All documentation has been focused on v2 APIs. There are Orgs which have large scale Pulsar clusters and use V1 apis. There is no way we can deprecate V1 api and it has to be maintained until we find

Re: [DISCUSS] Cancel the configuration of autoAck in Function framework

Regarding your question "why AUTO_ACK is designed this way" I think at the time when it's firstly implemented, the AUTO_ACK is just a convenient way to help user ack the message. We can discuss the gap between expected behavior and actual behavior and try to resolve or simplify it. On

[DISCUSS] [PIP-165] Auto release client useless connections

Hi Pulsar community: I open a pip to discuss Auto release client useless connections. link: [PIP-165] Auto release client useless connections · Issue #15516 · apache/pulsar (github.com)

Re: Discuss about creating partitioned topic in V1

Thanks. @Matteo I will track this. Regards Jiwei Guo (Tboy) On Tue, May 10, 2022 at 7:37 AM Matteo Merli wrote: > Why I agree that it "looks like a bug", "walks like a bug" and "talks > like a bug"... > this was actually a "feature" :) > > not a good one, or with a good reason to exist, but

Re: [DISCUSS] Cancel the configuration of autoAck in Function framework

> For users, sink is also part of the function framework. ^^ Is this written inside any Pulsar documentation? If you look the code closely, the source and sink are actually configurable in Java runtime. User can actually provide their own source/sink implementation. On 2022/05/10 01:38:48

[GitHub] [pulsar-manager] urfreespace merged pull request #460: fix: launch error with log lib conflict

urfreespace merged PR #460: URL: https://github.com/apache/pulsar-manager/pull/460 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

New Pulsar Website is Coming Soon!

Hi everyone, The New Pulsar Website (beta) has been running for more than 3 months. We've optimized the website based on the feedback from the New Pulsar Website Survey [1]. Now everything goes fine except few known issues: - Search function may not work very well - Some pages are not completely

Re: Call for projects and mentors for OSPP 2022

Hi guys, thanks for your project ideas. I have helped submit your ideas to the OSPP website. I believe you have received the invitation emails, PTAL. Next, the interested students will email you to learn more about your project, please be patient with their questions. :> Reference: [1] Mentor

Re: [DISCUSS] Cancel the configuration of autoAck in Function framework

> AUTO_ACK setting means if the function runtime will ack messages or not. > ("function runtime" here specifically refers to the JavaInstanceRunnable. If > the ack happens inside a sink's implemented write method, it's not auto-ack). The description of the official website document is：Whether

Re: [DISCUSS] Cancel the configuration of autoAck in Function framework

Thanks reply, > If AUTO_ACK is TRUE, then the JavaInstanceRunnable will be acking messages. > If AUTO_ACK is FALSE, then the acking will be done by Sink implementation. A little confused, I want to know why AUTO_ACK is designed this way. I'll give another example: > If AUTO_ACK is TRUE, then

Re: Discuss about creating partitioned topic in V1

Why I agree that it "looks like a bug", "walks like a bug" and "talks like a bug"... this was actually a "feature" :) not a good one, or with a good reason to exist, but something we've been trying not to break. I'm not going to dig into the "wrong" reasoning on why this was done in the first

Re: Discuss about creating partitioned topic in V1

+1 I agree totally. It is a bug Enrico Il Lun 9 Mag 2022, 20:59 Michael Marshall ha scritto: > Great find, Jiwei Guo. I agree that this should be classified as a bug > and that we should change the V1 implementation so that a topic can > only be created if its namespace already exists. > >

Re: Discuss about creating partitioned topic in V1

Great find, Jiwei Guo. I agree that this should be classified as a bug and that we should change the V1 implementation so that a topic can only be created if its namespace already exists. Thanks, Michael On Mon, May 9, 2022 at 7:13 AM guo jiwei wrote: > > Hi, community: >I found that in the

Re: Build Pulsar Server on Java 17- too strict ?

We have already had several discussions on this subject, on the by-weekly community call, on the PIP proposal and finally the PIP vote. It is not that the PR came out of the blue. Obviously every decision can be re-visited if there are additional details, though it would be better if we get the

Re: [DISCUSS] Cancel the configuration of autoAck in Function framework

Thanks for this detailed discussion about processing guarantee and ack. These two settings are together affecting the behavior of a running function. One thing I want to clarify is: AUTO_ACK setting means if the function runtime will ack messages or not. ("function runtime" here specifically

Re: Build Pulsar Server on Java 17- too strict ?

+1 for requiring JDK11 and prepare for JDK17 On 2022/05/09 11:03:27 Enrico Olivelli wrote: > I am sorry, > I have missed this thread. > > I believe that requiring JDK17 to build and especially to RUN the > Pulsar broker is not a good idea currently. > Many enterprises, especially the bigger, or

[GitHub] [pulsar-client-node] Matt-Esch opened a new pull request, #215: prevent double callback segfault in client close

Matt-Esch opened a new pull request, #215: URL: https://github.com/apache/pulsar-client-node/pull/215 There appears to be a race condition that causes the close callback to execute twice on close. I believe that a similar issue existed with the old synchronous api call in a async worker,

[DISCUSS] [PIP-160] ManagedLedger decorator for batch append enties

Hi Pulsar community: I open a pip to discuss ManagedLedger Decorator for batch append enties. link: https://github.com/apache/pulsar/issues/15370 Thanks, Feng

Re: [VOTE] PIP-156: Build and Run Pulsar Server on Java 17

PIP-156 PR https://github.com/apache/pulsar/pull/15264 has been merged to master branch. Please notice that Java 17 is now required for building Pulsar master branch. btw. https://sdkman.io/ is handy for managing multiple JDK versions in local development environments. -Lari On 2022/04/20

[DISCUSS] Cancel the configuration of autoAck in Function framework

Hi, guys: I found out that autoAck configuration in function framework now affects Delivery semantics, and make it difficult for users to understand. Refer to the following two scenarios. 1. If the user understands that the semantics of Guarantees shall prevail If the user set Guarantees ==

[GitHub] [pulsar-manager] urfreespace opened a new pull request, #460: fix: launch error with log lib conflict

urfreespace opened a new pull request, #460: URL: https://github.com/apache/pulsar-manager/pull/460 fix launch error due to log lib conflict -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the