> As it is, we already need to discuss EOL for 2.7 and 2.8.
Agree. We should clarify this one.
I think we can stop to provide new releases for 2.7
and only security or critical bugs for 2.8 (one more official release)
https://github.com/apache/pulsar/issues/15966 will make the
release strategy cl
I am concerned that we have too many active release branches, and planning
to follow 2.11.0 with 3.0.0 soon after feels like it will make that problem
worse. As it is, we already need to discuss EOL for 2.7 and 2.8.
Thanks,
Michael
On Mon, Oct 31, 2022 at 7:55 PM PengHui Li wrote:
> Releasing f
> I think we lose a single linearized view.
Which linearized view are we losing, and what is the role of that
linearized view? I think I might be missing why it is important. I
agree that consumers won't know about each unsuccessful attempted
acquisition of a bundle, but that seems like unnecessar
> This is already the case for both HTTP and pulsar protocols
We have a flag to control the value of authentication data. See
https://github.com/apache/pulsar/blob/82237d3684fe506bcb6426b3b23f413422e6e4fb/pulsar-proxy/src/main/java/org/apache/pulsar/proxy/server/ProxyConnection.java#L316-L322
.
>
The Apache Pulsar team is proud to announce Apache Pulsar version 2.10.2.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subs
GitHub user momo-jun added a comment to the discussion: How to achieve the
effect of maximum delay time in retransmission backoff mechanism
@codelipenghui @startjava Thanks for pointing this out. The doc update only
covered the next version. I will get it fixed.
GitHub link:
https://github.c
Releasing from the master branch will bring more uncertainty, no?
We have fixed many regressions that were introduced to branch-2.11.
If we cut a new branch-2.11 based on the master branch. Maybe new
regressions
will happen again. This may make us wait another month to have a 2.11.0
release.
IMO,
Thanks for starting this thread, Zixuan.
For additional context, I provided some related feedback in comments
on this PR: https://github.com/apache/pulsar/pull/18130.
> So I suggest the proxy should always forward the authentication data from
> the client.
This is already the case for both HTTP
GitHub user michaeljmarshall added a comment to the discussion: why "egatively
acknowledged before the acknowledgment timeout"?? after Can't?
That's correct.
GitHub link:
https://github.com/apache/pulsar/discussions/18248#discussioncomment-4021986
This is an automatically sent email for
I have not followed the branch-2.11 work closely, but I think it makes
sense to re-create branch-2.11 from the current master.
We created branch-2.11 almost 3 months ago. Re-creating the branch
will prevent unnecessary delay on new features added over the past 3
months.
If we follow through with
GitHub user michaeljmarshall added a comment to the discussion: Flink consumes
pulsar data, and an error is reported that the subscription cannot be found
Do you have inactive topic deletion enabled? Are there any relevant logs with
the subscription name in them?
GitHub link:
https://github.
GitHub user startjava added a comment to the discussion: How to achieve the
effect of maximum delay time in retransmission backoff mechanism
@codelipenghui hahaha , code run result and new doc same ! my code is right
thank you !
GitHub link:
https://github.com/apache/pulsar/discussions/18261
GitHub user codelipenghui added a comment to the discussion: How to achieve the
effect of maximum delay time in retransmission backoff mechanism
It should be documentation issue
The latest documentation works fine
https://pulsar.apache.org/docs/next/concepts-messaging/#negative-acknowledgment
GitHub user startjava added a comment to the discussion: How to achieve the
effect of maximum delay time in retransmission backoff mechanism
@codelipenghui
```
@RequestMapping("sendMessage5")
public String sendMessage5() throws PulsarClientException {
String messageValue = "我是
Hi all,
I want to discuss the authentication data issue, which affects the
authorization operation.
For the default to authorization provider, we only used the role to check
the permission, the authentication data was ignored. When a user wants to
customize an authorization provider, the user can
GitHub user BohanZhang0222 edited a discussion: Flink consumes pulsar data, and
an error is reported that the subscription cannot be found
2022-10-31 10:08:30,616 WARN
org.apache.pulsar.client.admin.internal.BaseResource [] -
[http://dip-dmp-pulsar-prod.chj.cloud:8080/admin/v2/persis
Hello Pulsar fellows,
I think that too much time passed since we wanted to cut 2.11.
The branch-2.11 contains some code used by no one.
In the meantime many features went into master branch,
I don't think that it is worth it to cut a release from branch-2.11
and start with something that is alr
17 matches
Mail list logo
