[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #169: Move config docs to /reference and improve docs gen scripts

SignorMercurio opened a new pull request, #169: URL: https://github.com/apache/pulsar-site/pull/169 @urfreespace PTAL carefully. -- 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 comme

[GitHub] [pulsar-site] Technoboy- commented on a diff in pull request #167: [Don't Merge] Pulsar 2.11.0 release notes

Technoboy- commented on code in PR #167: URL: https://github.com/apache/pulsar-site/pull/167#discussion_r950852597 ## site2/website/release-notes.md: ## @@ -1,6 +1,486 @@ ## Apache Pulsar Release Notes +### 2.11.0 + 2022-08-16 + +### Important notice +- Rename Pulsar tx

[GitHub] [pulsar] tisonkun edited a discussion: Strange failure when build Pulsar Docker image on M1

GitHub user tisonkun edited a discussion: Strange failure when build Pulsar Docker image on M1 These issues should be all answered by https://github.com/apache/pulsar/issues/12944#issuecomment-1103444708. When debugging https://github.com/apache/pulsar/issues/12944, I encounter several stran

[GitHub] [pulsar] tisonkun edited a discussion: Strange failure when build Pulsar Docker image on M1

GitHub user tisonkun edited a discussion: Strange failure when build Pulsar Docker image on M1 UPDATED: These issues should be all answered by https://github.com/apache/pulsar/issues/12944#issuecomment-1103444708. When debugging https://github.com/apache/pulsar/issues/12944, I encounter seve

[GitHub] [pulsar] tisonkun edited a discussion: Strange failure when build Pulsar Docker image on M1

GitHub user tisonkun edited a discussion: Strange failure when build Pulsar Docker image on M1 **UPDATED: These issues should be all answered by https://github.com/apache/pulsar/issues/12944#issuecomment-1103444708.** --- When debugging https://github.com/apache/pulsar/issues/12944, I encoun

Performance issue in Pulsar with large fan-outs since Pulsar 2.8.2

Hi all, I'd like to get some more eyes on this long outstanding performance issue with large fan-outs (a large number of consumers for a single topic). The broker cache does not work as expected due to invalid changes introduced in version 2.8.2 by PR https://github.com/apache/pulsar/pull/12045.

[GitHub] [pulsar-site] Anonymitaet commented on a diff in pull request #167: [Don't Merge] Pulsar 2.11.0 release notes

Anonymitaet commented on code in PR #167: URL: https://github.com/apache/pulsar-site/pull/167#discussion_r950948327 ## site2/website/release-notes.md: ## @@ -1,6 +1,486 @@ ## Apache Pulsar Release Notes +### 2.11.0 + 2022-08-16 + +### Important notice +- Rename Pulsar t

[GitHub] [pulsar-site] Anonymitaet commented on a diff in pull request #167: [Don't Merge] Pulsar 2.11.0 release notes

Anonymitaet commented on code in PR #167: URL: https://github.com/apache/pulsar-site/pull/167#discussion_r948753697 ## site2/website/release-notes.md: ## @@ -1,6 +1,486 @@ ## Apache Pulsar Release Notes +### 2.11.0 + 2022-08-16 + +### Important notice +- Rename Pulsar t

[GitHub] [pulsar-site] Anonymitaet commented on a diff in pull request #167: [Don't Merge] Pulsar 2.11.0 release notes

Anonymitaet commented on code in PR #167: URL: https://github.com/apache/pulsar-site/pull/167#discussion_r950948327 ## site2/website/release-notes.md: ## @@ -1,6 +1,486 @@ ## Apache Pulsar Release Notes +### 2.11.0 + 2022-08-16 + +### Important notice +- Rename Pulsar t

RE: Enable "Update branch" Github button in pull requests

+1 Best, Zixuan On 2022/07/12 16:06:43 Nicolò Boschi wrote: > Hi all, > > I'd like to propose to enable the Github button "update branch" in the pull > requests. > > The main reason is that it helps when you want to rebase your pull to the > current master. > For instance today a fix for a fail

RE: [DISCUSS] Enable non-mandatory updating PR branches

+1 Best, Zixuan On 2022/08/18 13:01:58 tison wrote: > Hello, > > The short version > = > > Vote if you agree on enabling the non-mandatory updating PR branches > button, i.e., the "Always suggest updating pull request branches" GitHub > settings. > > The full version >

[GitHub] [pulsar-site] urfreespace merged pull request #170: fix version replace

urfreespace merged PR #170: URL: https://github.com/apache/pulsar-site/pull/170 -- 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: dev-unsubscr...@pulsar.a

[GitHub] [pulsar] BohanZhang0222 created a discussion: Flink Connector Exception: Failed to list subscribed topic partitions due to

GitHub user BohanZhang0222 created a discussion: Flink Connector Exception: Failed to list subscribed topic partitions due to ## Env Pulsar Version: 2.9.2 Flink Version: 1.14 ##Source Conf `{"topicNames":["persistent://autopilot/x01/autopilot-filter-iot-signal-canlog-x01-testtwo-partition-0"],

[GitHub] [pulsar] BohanZhang0222 edited a discussion: Flink Connector Exception: Failed to list subscribed topic partitions due to

GitHub user BohanZhang0222 edited a discussion: Flink Connector Exception: Failed to list subscribed topic partitions due to ## Env Pulsar Version: 2.9.2 Flink Version: 1.14 ##Source Conf `{"topicNames":["persistent://autopilot/x01/autopilot-filter-iot-signal-canlog-x01-testtwo-partition-0"],"

Re: [Discussion] PIP 198 - How to define [type] and [scope]?

Thank you tison and Zixuan! Agree on the following aspects: # 1. Remove 3 [scope]s - Remove [workflow] since it can be replaced with other scopes eg. "[feat][workflow] Add instructions for previewing website changes" can be written as "[feat][doc] Add instructio

[DISCUSS] Use Github project to track the multi clients development

Hi, all Currently, many features or bug fixes of some clients like the C++ client and Python client have not caught up with the Java client. For better tracking of these features or bug fixes, I have created a Github project called `Apache Pulsar / Multi Clients`[0] under the pulsar main repo. It

Re: [Discussion] PIP 198 - How to define [type] and [scope]?

Hi tison, Thanks for your suggestions! We have several questions on [build]: > build - all things related to the build system, including tools, deployment logic, maven changes, packaging logics, docker image, build scripts. # 1. "tools" What do you refer to? P

Re: [Discussion] PIP 198 - How to define [type] and [scope]?

Hi developers, Two quick questions need your vote! Which do you prefer? # 1. Use "branch" or "BP"? Choice A: [fix][broker][branch-2.9] xxx Choice B: [fix][broker][BP-2.9] xxx # 2. for the [scope], use "misc" or "chore"? [1] C

Re: [Discussion] PIP 198 - How to define [type] and [scope]?

A A Thanks Tao Jiuming > 2022年8月22日 下午12:47，Yu 写道： > > Hi developers, > > Two quick questions need your vote! > > Which do you prefer? > > > > # 1. Use "branch" or "BP"? > > Choice A: [fix][broker][branch-2.9] xxx > Choice B: [fix][broker][BP-2.9] xxx > > ~

Re: [VOTE]PIP-189: No batching if only one message in batch.

+1 (binding) Regards Jiwei Guo (Tboy) On Mon, Aug 8, 2022 at 11:17 AM PengHui Li wrote: > +1 (binding) > > Penghui > > On Tue, Jul 26, 2022 at 10:23 PM Zike Yang wrote: > > > +1 (non-binding) > > Great work! > > > > Thanks > > Zike Yang > > > > On Tue, Jul 26, 2022 at 7:31 PM Enrico Olivelli

Re: [Discussion] PIP 198 - How to define [type] and [scope]?

A, A Thanks, Yunze > 2022年8月22日 12:47，Yu 写道： > > Hi developers, > > Two quick questions need your vote! > > Which do you prefer? > > > > # 1. Use "branch" or "BP"? > > Choice A: [fix][broker][branch-2.9] xxx > Choice B: [fix][broker][BP-2.9] xxx > > ~~~

Re: [VOTE]PIP-189: No batching if only one message in batch.

Thank you all. Close the vote with 3 (+1) bindings and 4 (+1) non-bindings. Thanks, Xiaoyu Hou guo jiwei 于2022年8月22日周一 13:18写道： > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Mon, Aug 8, 2022 at 11:17 AM PengHui Li wrote: > > > +1 (binding) > > > > Penghui > > > > On Tue, Jul 26, 20

Re: [DISCUSS] [PIP-201] Extensions mechanism for Pulsar Admin CLI tools

The motivation and goal LGTM, but the API changes look very simple and hard to use. Do we have to implement all these interfaces for an admin extension? If yes, could you show an example in the proposal as a guidance? For example, if I just want to implement a simple command: ```bash ./bin/pulsar

Re: Performance issue in Pulsar with large fan-outs since Pulsar 2.8.2

Thank you for starting this important discussion, Lari. It seems the issue is in the way the `heap` list in the ManagedCursorContainer class is ordered. The heap is ordered by mark delete position, while cache eviction is determined by the slowest read position [0]. The PR [1] essentially says tha