Hi, Michael and Haiting,
Thanks for your suggestions, I’ve updated the PR, PTAL.
Thanks,
Yunze
> On Sep 8, 2022, at 14:41, Haiting Jiang wrote:
>
> Good point, Michael.
>
> Compile errors happen quite often when cherry-picking commits, even
> though there is no conflict
> but compile still
Hi Mingyu,
> it is a different dimension from router implementation
The permission control mechanism won't work without a new router.
> The control here is only from the perspective of operation and maintenance to
> reduce the impact of accumulated messages on new messages.
I think developer
Anonymitaet commented on PR #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71#issuecomment-1247541039
+1
> For example, I may prefer to add a slug for each label candidate like:
>
> - [ ] `doc-required` (Your PR needs to update docs and you will update
later)
>
Anonymitaet commented on code in PR #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71#discussion_r971488688
##
docbot/action.go:
##
@@ -13,10 +13,7 @@ import (
)
const (
- MessageLabelMissing = `Please provide a correct documentation label for
your PR.
-In
Hi Bo,
> In this case, the consumer can not receive any message again in the
> end. We have to fix it because it causes a loss of messages.
> I think we need to redefine the use of cumulative acks and not just
> solve the problem of receiving messages repeatedly.
>
There seems to be nothing wrong
GitHub user xuesongxs created a discussion: Will the error reported in the
bookie‘log cause the message in the Pulsar topic to be lost?
Will the error reported in the bookie‘log cause
Hi all,
I have drafted PIP-207: Add clientStats API for ProxyStats.
PIP link: https://github.com/apache/pulsar/issues/17625
This is my first PIP. Any advice would be greatly appreciated.
Here's a copy of the contents of the GH issue for your references:
Motivation
Add a new api name
k2la commented on issue #78:
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-1247477104
@jbmusso
I have same issue in my environment using your settings and sample code.
But no errors occur with master branch of `pulsar-client-node`.
Could you try with mast
gurleen-gks opened a new pull request, #488:
URL: https://github.com/apache/pulsar-manager/pull/488
### Motivation
Removing transitive dependencies for `log4j:log4j:1.2.17`
version 2.17.1 is already added in the dependencies
### Modifications
Excluding transitive dependenc
bharatbhushan1705 commented on issue #287:
URL:
https://github.com/apache/pulsar-helm-chart/issues/287#issuecomment-1247328289
Hello Team,
Is there someone who can help me to proceed further?
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
GitHub user visortelle created a discussion: Missing namespaces metrics
Hello. I have the following question:
Let’s say I have two topics:
- persistent://tenant-1/ns-1/to-1
- persistent://tenant-1/ns-2/to-2
For each of the topics, there is pulsar-perf produce -mk random that
runs more for
GitHub user agrahul89 created a discussion: Healthcheck in pulsar-admin rest api
Is healthcheck endpoint not available pulsar-admin rest api similar to what is
available with command line pulsar-admin?
> pulsar-admin brokers healthcheck
Only rest endpoints I am able to see related to broker ar
After my previous email, I received a question about Pulsar
backpressure solutions:
"Why can't we use Reactive frameworks here?"
That's a good question.
Pulsar isn't implemented in a way where Reactive frameworks would be
easily applicable or make sense in the Broker. (For implementing the
REST A
Hi Haiting, Michael ,
I tested an example, and there may be some problems when using the sub
reset cursor and cumulative ack at the same time. e.g
```
Message message = null;
for (int i = 0; i < 3; i++) {
message = consumer.receive();
}
admin.topics().resetCursor(topic, subName, MessageId.ea
Thank you Mattison for starting the discussion.
Just adding some more context.
In general, every type of processing pipeline solution needs a solution
for backpressure. This could mean different types of solutions for
different goals, depending on the context. Usually a backpressure
solution is s
nodece commented on code in PR #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71#discussion_r970590996
##
docbot/action.go:
##
@@ -13,10 +13,7 @@ import (
)
const (
- MessageLabelMissing = `Please provide a correct documentation label for
your PR.
-Instruc
nodece merged PR #72:
URL: https://github.com/apache/pulsar-test-infra/pull/72
--
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.ap
Hi Enrico,
I can understand the concern about the validation of the topic
string key in the map we are using. In this case is it good to have
Map topicToMessage? It will help us to validate that the
message truly belongs to the topic/partition.
Thank you,
Tarun.
On Wed, 14 Sept 2022 at 07:
tisonkun commented on code in PR #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71#discussion_r970553659
##
docbot/action.go:
##
@@ -13,10 +13,7 @@ import (
)
const (
- MessageLabelMissing = `Please provide a correct documentation label for
your PR.
-Instr
tisonkun commented on PR #72:
URL: https://github.com/apache/pulsar-test-infra/pull/72#issuecomment-1246487106
See the result at:
https://github.com/tisonkun/pulsar-test-infra/actions/runs/3051651757/jobs/4920133211
--
This is an automated message from the Apache Git Service.
To respond t
tisonkun opened a new pull request, #72:
URL: https://github.com/apache/pulsar-test-infra/pull/72
cc @nodece
--
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
tisonkun commented on code in PR #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71#discussion_r970539627
##
docbot/action.go:
##
@@ -13,10 +13,7 @@ import (
)
const (
- MessageLabelMissing = `Please provide a correct documentation label for
your PR.
-Instr
nodece commented on PR #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71#issuecomment-1246441936
@maxsxu @tisonkun @Anonymitaet Please help to review, thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
nodece opened a new pull request, #71:
URL: https://github.com/apache/pulsar-test-infra/pull/71
### Motivation
Remove gdoc link, using the following format instead.
https://user-images.githubusercontent.com/16235121/190106178-22983986-a769-42e4-9bf9-ef5a9d0ddb4b.png";>
--
Thi
Yes, I agree. BTW, we can continue the discussion in your proposal.
https://lists.apache.org/thread/3vd136jfhh7g0mhgwxrnqk7mx69qy17m
Thanks,
Yunze
> On Sep 14, 2022, at 14:17, Tarun Annapareddy
> wrote:
>
> Hi,
> There is a concern about the validation of the topic string key in the
> map
25 matches
Mail list logo
