This issue is used for collecting the features planned for release 2.6.0.
approved doc-addedmerged no-need-docmergedmerged doc-addedreview-requiredapprovedreview-required doc-addedreview-requiredmergedmergedmergedmergedapprovedmergedmergedmerged doc-addedmergedmergedmerged doc-addedmergedmergedapprovedmergedmergedmergedmergedmerged doc-requiredmerged doc-required-it is generated automaticallymerged doc-addedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmerged doc-addedapprovedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedmergedPlease link or comment the issues here.
hopefully this bug #4976 can be fixed in release 2.6.0 :-D
Both pulsar and bk should support ipv6, such as #5713
Some users are expecting Pulsar transaction and KOP in the new release.
Custom functions runtime
@codelipenghui we need to make sure Pulsar 2.6.0 is released with JDK 11.
@codelipenghui
I've replaced some doc-required tags w/ doc-added since docs have been added by @Huanli-Meng and me.
Thanks @Anonymitaet
@codelipenghui
The item Custom functions runtime does not have a PR link.
I've searched Custom functions runtime w/ the label milestone 2.6.0 and got the result.
Is [Pulsar Functions] Support config admin CLI in funtions runtime #6681 the one I'm looking for?
@Anonymitaet Looks like this item made it way to the list because of my proposal (which actually meant custom language runtime like .net) which doesn't seem to even be planned for implementation, so it should be removed.
@Lanayx OK, thanks.
@codelipenghui Does the last item Work on JDK 11 has a PR link?
I wish that the bug in negative acknowledgements for batch messages (#6869) would also be fixed in 2.6.0 . It would make the improvement for batch message acknowledgements PIP-54 / #6052 more complete.
@lhotari I have started the 2.6.0 candidate, we can plan #6869 in 2.6.1.
@codelipenghui shall we add the following item to 2.6.0 release notes as @sijie points here?
or
?
@codelipenghui @sijie @merlimat
I retied the issue I faced with 2.5.0 with pulsar-2.6.0-candidate-1.
http://mail-archives.apache.org/mod_mbox/pulsar-users/202003.mbox/%3CCAPDOW74LN3WtdhpG_cgCCSg9MuMmkNV6giCGD5p%3DW1wWji0W7w%40mail.gmail.com%3E
But I'm still facing inconsistent order in between consumers with the default way (splitting range).
I didn't face it if I switch it to use consistent hashing.
So, this seems not resolved yet.
https://github.com/apache/pulsar/issues/6554
https://github.com/apache/pulsar/pull/6977
If 2.6.0 will be released without fixing the above, consistent hashing should be the default ?
I created a how to reproduce doc, so please take a look.
https://github.com/feeblefakie/misc/blob/master/pulsar/HOW-TO-REPRODUCE.md
@feeblefakie Thanks for your update. https://github.com/apache/pulsar/pull/7106 is to fix the order problem in the Key_Shared subscription, It looks there are some problems with the auto-split mechanism. I will take a look later.
close this issue since 2.6.0 was released.
Most helpful comment
Some users are expecting Pulsar transaction and KOP in the new release.