[GitHub] [pulsar] lhotari added a comment to the discussion: What's the best practice to build java-test-image?

2022-07-17 Thread GitBox
GitHub user lhotari added a comment to the discussion: What's the best practice to build java-test-image? There seems to be some network issues. In the output, you can see: > [INFO] Err:6 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist > [INFO] Could not connect to mirrors.ubuntu.com:80 (19

[GitHub] [pulsar] tisonkun created a discussion: How to build java-test-image on Apple M1?

2022-07-17 Thread GitBox
GitHub user tisonkun created a discussion: How to build java-test-image on Apple M1? cc @lhotari Today I'm trying to build java-test-image on Apple M1. Run `build/build_java_test_image.sh` and get: ``` [ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.13:build (default

[GitHub] [pulsar-helm-chart] mattisonchao opened a new pull request, #277: Bump Apache Pulsar version to 2.9.3

2022-07-17 Thread GitBox
mattisonchao opened a new pull request, #277: URL: https://github.com/apache/pulsar-helm-chart/pull/277 ### Motivation Bump Apache Pulsar version to 2.9.3 ### Modifications - Bump Apache Pulsar version to 2.9.3 ### Verifying this change - [x] Make sure that

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

2022-07-17 Thread Yunze Xu
In addition to #16202, there is a following PR to support the correct ACK implementation for chunked messages. It should depend on #16202 But I think I can submit an initial PR this week and change the tests after #16202 is merged. Thanks, Yunze > 2022年7月18日 11:22,PengHui Li 写道: > > Hi all,

[GitHub] [pulsar] tisonkun added a comment to the discussion: What's the best practice to build java-test-image?

2022-07-17 Thread GitBox
GitHub user tisonkun added a comment to the discussion: What's the best practice to build java-test-image? Each time it failed in different step but all about cannot download from a remote place. Perhaps it's about network issues. GitHub link: https://github.com/apache/pulsar/discussions/166

[DISCUSS] Apache Pulsar 2.11.0 Release

2022-07-17 Thread PengHui Li
Hi all, We released 2.10.0 three months ago. And there are many great changes in the master branch, including new features and performance improvements. - PIP 74: apply client memory to consumer https://github.com/apache/pulsar/pull/15216 - PIP 143: Support split bundles by specified boundaries h

Re: [VOTE] PIP-184: Topic specific consumer priorityLevel

2022-07-17 Thread PengHui Li
+1 Penghui On Mon, Jul 18, 2022 at 10:15 AM Zike Yang wrote: > +1 > > Thanks > > > On Fri, Jul 15, 2022 at 3:58 PM Dave Maughan > wrote: > > > > Hi Pulsar Community > > > > I would like to start a VOTE on "PIP-184: Topic specific consumer > > priorityLevel". > > > > The proposal can be read at

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

2022-07-17 Thread Anon Hxy
Hi Enrico > it is always a good idea to not create a batch message I agree this. So maybe I need a little work to fix the internal tests.:) Thanks Xiaoyu Hou Enrico Olivelli 于2022年7月15日周五 17:29写道: > Thanks for driving this initiative. > > I think that it is better to not add a configuration fl

Re: [VOTE] PIP-184: Topic specific consumer priorityLevel

2022-07-17 Thread Zike Yang
+1 Thanks On Fri, Jul 15, 2022 at 3:58 PM Dave Maughan wrote: > > Hi Pulsar Community > > I would like to start a VOTE on "PIP-184: Topic specific consumer > priorityLevel". > > The proposal can be read at https://github.com/apache/pulsar/issues/16481 > > and the discussion thread is available

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

2022-07-17 Thread PengHui Li
Hi Haiting, > For this point, like I wrote in the reply to Asaf, I still think the cost of maintaining the consumers would be a little too high, especially the lifecycle management part. It's quite complicated in replicator already. Yes, I see it. Makes sense. Without the replicator, it looks lik

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

2022-07-17 Thread Haiting Jiang
Hi Penghui, > I had a conversation with Asaf, looks like we can use the RawReader for a > shadow topic internally to consume > messages from the original topic. So that we don't need to introduce > `shadow_message_id`, and don't need to introduce > changes to the replicator. For this point, like

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

2022-07-17 Thread Haiting Jiang
Hi Asafa, On 2022/07/13 08:15:59 Asaf Mesika wrote: > Thanks for the detailed answer. I have a few follow-up questions: > > 1. Can you clarify how data is flowing exactly. Specifically, from source > topic broker to shadow topic broker? I tried to follow the PIP again to > understand that, especi