Congratulations
Enrico
Il Mar 15 Feb 2022, 08:07 PengHui Li ha scritto:
> The Apache Pulsar Project Management Committee (PMC) has invited Li Li
> https://github.com/urfreespace to become a committer and we are pleased to
> announce that he has accepted.
>
> Li Li has done a great contribution
> It is not clear to me who is the consumer of this BOM.
I was thinking that using a Maven BOM file [1] could be useful when
implementing "PIP 62: Move connectors, adapters and Pulsar Presto to
separate repositories" [2].
Pulsar Adapters is the only part of PIP-62 that has been moved. The
The Apache Pulsar Project Management Committee (PMC) has invited Li Li
https://github.com/urfreespace to become a committer and we are pleased to
announce that he has accepted.
Li Li has done a great contribution to Pulsar Website, documentation.
Welcome and Congratulations, Li Li!
Please join
Hi all,
The PR https://github.com/apache/pulsar/pull/14288 needs more eyes to
unblock the 2.10.0 release.
The PR fixes a breaking change in the branch-2.9, branch-2.8, and master
branches.
Thanks,
Penghui
On Tue, Feb 15, 2022 at 12:32 PM PengHui Li wrote:
> Hi all
>
> Please help review this
Sorry Michael
There is a breaking change introduced in branch-2.8.
Sorry for that I forget to update the 2.8.3 release process,
Only update the context in 2.9.2 and 2.10.0.
We just confirmed yesterday that this is a breaking change,
I was just suspicious before, so do not share the information
Hi Micheal
Here is the context https://github.com/apache/pulsar/pull/14288
it fixed a breaking change in branch-2.8. Without this fix we will introduce
breaking change in 2.8.3
Thanks,
Penghui
On Tue, Feb 15, 2022 at 1:16 PM Michael Marshall
wrote:
> Hi Penghui,
>
> Do we have an issue or a
Hi Penghui,
Do we have an issue or a more specific description of the "breaking
change" and its fix?
This bug is holding up the 2.8.3 and 2.9.2 releases, but you haven't
shared any specific details. Given that in the 2.10 thread, you say
Tboy is working on a fix, it would be great if you or Tboy
Hi Penghui,
Thanks for your note. Unfortunately, I sent out the VOTE email for
2.8.3 before I read this email. Please let me know when there is a fix
in place. In this case, we'll need to create an RC 2.
Thanks,
Michael
On Mon, Feb 14, 2022 at 10:38 PM PengHui Li wrote:
>
> Hi Michael,
>
> I
This is the first release candidate for Apache Pulsar, version 2.8.3.
It fixes the following issues:
https://github.com/apache/pulsar/compare/v2.8.2...v2.8.3-candidate-1
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we are
Hi Michael,
I noticed the tag v2.8.3-candidate-1 has been created,
as I updated in 2.9.2 and 2.10.0 release emails,
There is a breaking change introduced by
https://github.com/apache/pulsar/pull/13383
We are working on a fix for now.
Regards,
Penghui
On Fri, Feb 11, 2022 at 7:37 AM Neng Lu
Hi all
Please help review this PR https://github.com/apache/pulsar/pull/14283
which should be a blocker for the 2.10.0 release.
Tboy is working on another fix to fix the breaking change introduced in
https://github.com/apache/pulsar/pull/13383.
After the PR is available for review, I will update
- Verified the signature
- Start the standalone and checked message publish and consumption
- Validate Cassandra connector
- Validate stateful function
Hi Lari, I have checked the CI status for branch-2.7
https://github.com/apache/pulsar/commits/branch-2.7
There are 4 failed tests, could you
blankensteiner commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039534679
Ah, yes it's here:
https://github.com/apache/pulsar/blob/master/pulsar-common/src/main/proto/PulsarApi.proto
and we generated the cs-file based on version 281163b of
Il giorno lun 14 feb 2022 alle 18:51 Christophe Bornet <
bornet.ch...@gmail.com> ha scritto:
> For plugins that are part of the main project, you get the dependencies
> from the parent POM. But for third-party plugins (including pulsar-io,
> protocol handlers and proxy-extensions),
So the
For plugins that are part of the main project, you get the dependencies
from the parent POM. But for third-party plugins (including pulsar-io,
protocol handlers and proxy-extensions), you generally don't want to
inherit from the Pulsar parent POM and it would be great to be able to
import a BOM
The ASF has a number of resources created from decades of fostering hundreds of
software communities in their missions to build amazing software components.
One of the committees is the Community Development PMC (ComDev)
Please review the following page:
ddieruf commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039344616
First, please forgive my potential lack of grpc knowledge...
I am making the assumption that the main Pulsar project produces some sort
of .proto definition for a
haphut opened a new issue #193:
URL: https://github.com/apache/pulsar-client-node/issues/193
The C++ client does not seem to use the property `type`. Yet [it has been
marked as
Christophe,
It is not clear to me who is the consumer of this BOM.
Java clients should depend on pulsar-client
Pulsar IO and Functions have their own dependencies.
So what's the target? Protocol Handlers? Servlets? Proxy extensions?
Enrico
Il Lun 14 Feb 2022, 15:05 Nicolò Boschi ha scritto:
Big +1
Le lun. 14 févr. 2022 à 14:54, Nicolò Boschi a
écrit :
> Dear Pulsar community,
>
>
> I would like to start a discussion about having a plan to make Pulsar
> runtime-compatible with JDK 17.
>
>
> The goal is to run Pulsar using JDK17 at runtime, benefitting from the
> latest JVM
Great idea!
+1
Il giorno mar 8 feb 2022 alle ore 12:18 Christophe Bornet <
bornet.ch...@gmail.com> ha scritto:
> Hi everyone,
>
> I'd like to open a discussion on PIP 141 : Pulsar BOM
>
> The PIP is here : https://github.com/apache/pulsar/issues/14168
>
> ## Motivation
>
> When designing NAR
Dear Pulsar community,
I would like to start a discussion about having a plan to make Pulsar
runtime-compatible with JDK 17.
The goal is to run Pulsar using JDK17 at runtime, benefitting from the
latest JVM performance improvements and features.
The non-goal is to deprecate JDK8 or JDK11
blankensteiner commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039101820
Not sure I understand what you mean by that?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
ddieruf commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039090818
Hi, thank you for that. Does the master branch follow the latest version of
Pulsar?
--
This is an automated message from the Apache Git Service.
To respond to the message,
+1
Checks:
- Checksum and signatures
- Compile from source w JDK11
- Validate Pub/Sub and Java Functions [1]
- Validate Connectors [1]
- Validate Stateful Functions [1]
[1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
Thanks,
Haiting
On 2022/02/11 13:47:50 Lari
blankensteiner commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039056022
Hi @ddieruf
It's done using https://protogen.marcgravell.com/
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
Hi Lari,
There are 5 open PRs
https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.10.0
and #14225 is a release blocker.
For #13376 and #13341, we are preparing the testing, to make sure they can
safely ship to 2.10.0
For #10478, it's a critical fix for the current message
hassanzia32 commented on pull request #190:
URL:
https://github.com/apache/pulsar-client-node/pull/190#issuecomment-1039027608
Is there a timeline for when the 1.6.0 version is scheduled to be released?
--
This is an automated message from the Apache Git Service.
To respond to the
Hi Lari,
We have another issue that needs to confirm if it will introduce break
changes in 2.9.2,
Expected to have a result tomorrow, it related to
https://github.com/apache/pulsar/pull/13383,
We're doing more testing to make sure it doesn't introduce unexpected
behavior.
Regards,
Penghui
On
ddieruf opened a new issue #99:
URL: https://github.com/apache/pulsar-dotpulsar/issues/99
As I learn more about the project, I was wondering how
`DotPulsar.Internal.PulsarApi` is generated? To be honest I was expecting to
see a github workflow (or some automation) that creates the .cs but
When is 2.9.2 Candidate 3 planned?
What changes will it include? All current changes in branch-2.9 ?
The version has already been set to 2.9.3-SNAPSHOT in branch-2.9 with
https://github.com/apache/pulsar/pull/14089 . If we do 2.9.2 with all current
changes from branch-2.9, the commit for PR
> After the features are completed, I will create the new 2.10 branch, and
> only apply
> the critical bug fixes, regression fixes. So that we can have adequate
> testing on branch-2.10
Hi Penghui,
What's the status of 2.10.0 release? What features aren't complete?
In PIP 47
Please help to verify this release. Thank you
-Lari
On 2022/02/11 13:47:50 Lari Hotari wrote:
> This is the first release candidate for Apache Pulsar, version 2.7.5.
>
> It contains the following commits after the previous release:
>
blankensteiner commented on issue #98:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/98#issuecomment-1038783547
Hi @GeroL
Cool, let me know when you feel it is ready for a review :-)
--
This is an automated message from the Apache Git Service.
To respond to the message,
34 matches
Mail list logo
