You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Dan Smith <da...@vmware.com> on 2022/01/04 22:18:45 UTC
[VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://dist.apache.org/repos/dist/dev/geode/kafka-connector-1.1.0/
Github: https://github.com/apache/geode-kafka-connector/tree/rel/v1.1.0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Nabarun Nag <nn...@vmware.com>.
+1
Checked with building source and running tests.
Regards
Naba
________________________________
From: Dan Smith <da...@vmware.com>
Sent: Tuesday, January 4, 2022 2:37 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
This is the same release I started a VOTE on in December and canceled due to Christmas. Here was my earlier comment on where this release is coming from:
On Dec 16, 2021 11:33 AM, Dan Smith <da...@vmware.com> wrote:
This is related to the earlier discussion about the kafka connector. This code was already linked from the confluent hub, but I want to make sure we're in compliance with the apache release policy.
To create this release, I took the source code and binaries Naba mentioned and compared them with the rel/1.1.0 source tag and the results of building that tag. They were identical except for the build date in the metadata.json file for the binary.
I added gpg and sha256sum signatures and uploaded the artifacts to the apache staging repo for you all to review.
I checked out the license, notice, and source code headers and everything looked ok to me from that perspective.
In the future, we may want to release this in sync with the rest of the geode artifacts, but for now I'm just trying to create an official release that follows the release policy - https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Frelease-policy.html&data=04%7C01%7Cnnag%40vmware.com%7Ceb251e5e0a4f42bf46e108d9cfd2db04%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769326818200926%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=h%2BC1DQJsrqYTbs1nDOvdKvnr73SSeEtGEpMU3IyPS9o%3D&reserved=0
________________________________
From: Dan Smith <da...@vmware.com>
Sent: Tuesday, January 4, 2022 2:18 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cnnag%40vmware.com%7Ceb251e5e0a4f42bf46e108d9cfd2db04%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769326818200926%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=9Ompca49Q%2FGwVVxp6JwYFW%2FR03aAjAxz5TdQGACAaRw%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cnnag%40vmware.com%7Ceb251e5e0a4f42bf46e108d9cfd2db04%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769326818200926%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ulk3r0c7kttqzeb9i1GGY%2Bmy8CVNdKNQE0gDrLgX8fE%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Dan Smith <da...@vmware.com>.
This is the same release I started a VOTE on in December and canceled due to Christmas. Here was my earlier comment on where this release is coming from:
On Dec 16, 2021 11:33 AM, Dan Smith <da...@vmware.com> wrote:
This is related to the earlier discussion about the kafka connector. This code was already linked from the confluent hub, but I want to make sure we're in compliance with the apache release policy.
To create this release, I took the source code and binaries Naba mentioned and compared them with the rel/1.1.0 source tag and the results of building that tag. They were identical except for the build date in the metadata.json file for the binary.
I added gpg and sha256sum signatures and uploaded the artifacts to the apache staging repo for you all to review.
I checked out the license, notice, and source code headers and everything looked ok to me from that perspective.
In the future, we may want to release this in sync with the rest of the geode artifacts, but for now I'm just trying to create an official release that follows the release policy - https://www.apache.org/legal/release-policy.html
________________________________
From: Dan Smith <da...@vmware.com>
Sent: Tuesday, January 4, 2022 2:18 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cdasmith%40vmware.com%7C4ea1c82a07a348a28efe08d9cfd03470%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769315404324461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=vdEwrWUbhikvadJb1AYHQt2wannGXODwa%2Ft2l2TXtnQ%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cdasmith%40vmware.com%7C4ea1c82a07a348a28efe08d9cfd03470%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769315404324461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6KCZtjdYZ%2FhCCMO6H6NGeSWL0DcQBYvkS3xRxWkh5B8%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Dan Smith <da...@vmware.com>.
It's past the announced deadline and we have enough votes to close the vote.
Voting status
==========
+1: 3 binding votes
* Nabarun Nag (PMC member)
* Donal Evans (PMC member)
* Jason Huynh (PMC member)
+0: one vote
* Owen Nichols (Committer)
-0: zero votes
-1: zero votes
The voting meets the requirements of at least 3 PMC members with +1 votes and has the required majority of +1 votes.
Apache Geode Kafka Connector 1.1.0 has passed the vote and we will finalize the release shortly.
Thanks!
-Dan
________________________________
From: Donal Evans <do...@vmware.com>
Sent: Thursday, January 13, 2022 10:18 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
+1 on releasing this
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 11, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
+1 to move along with this release.
Here is the URI of the component archive specification set by Confluent[1]. Our first delivery had to be changed to meet these requirements.
Regards
Naba
[1]https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.confluent.io%2Fhome%2Fconnect%2Fconfluent-hub%2Fcomponent-archive.html&data=04%7C01%7Cdasmith%40vmware.com%7C67bc29ac823b49a4733408d9d6c115b4%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637776947052247021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BpkOe5bQQInlr9yMtrrWI9rhBR9RUkg7YHdZVjiLn%2Fw%3D&reserved=0
________________________________
From: Jason Huynh <jh...@vmware.com>
Sent: Tuesday, January 11, 2022 9:35 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
+1 for this release
On 1/6/22, 9:22 AM, "Dan Smith" <da...@vmware.com> wrote:
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Agreed, I think we'll want to do another release later to pickup the latest geode and log4j. The lack of RC1 is intentional - this is creating an official release based on what was already linked from the confluent hub.
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Good catch! I created GEODE-9925 for the missing dependencies.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
Can you clarify which things are in conflict? I think the file name for geode is not a hard requirement, just a convention we picked. Also the location of LICENSE and NOTICE files - is there some confluent requirement? Apache says those files should be at the top level for a source distribution, but I'm not clear about a binary distribution. For example, our jar files put them under META-INF, which I think is the java convention.
My inclination is to continue with this release as is and create a follow up release that updates log4j and the LICENSE, NOTICE files, so I'm leaving this VOTE open in hopes of getting some more votes.
-Dan
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 4, 2022 5:13 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
As it is primarily created for Confluent Marketplace we need to follow the steps required for hosting in the marketplace, which included how things are to be named, folder structure etc.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
We can definitely add the missing licenses and wait for 1.12.8 release of Apache Geode to update those dependencies.
Regards
Naba
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Tuesday, January 4, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cdasmith%40vmware.com%7C67bc29ac823b49a4733408d9d6c115b4%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637776947052247021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=MYpLBAaZ4Fkm9GFwjlts1Xsg3uvMf3lHRrm1jXrWE30%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cdasmith%40vmware.com%7C67bc29ac823b49a4733408d9d6c115b4%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637776947052247021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ahC7dFpWhiv6burrEDlW1n4LPe8iyqMec7jsvSwA8Dc%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Donal Evans <do...@vmware.com>.
+1 on releasing this
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 11, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
+1 to move along with this release.
Here is the URI of the component archive specification set by Confluent[1]. Our first delivery had to be changed to meet these requirements.
Regards
Naba
[1]https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.confluent.io%2Fhome%2Fconnect%2Fconfluent-hub%2Fcomponent-archive.html&data=04%7C01%7Cdoevans%40vmware.com%7C976d5d23599d45e7ae7b08d9d564d0a5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637775451252718005%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=YbLpP1ev8qOgsQ5v9GS%2F%2FQjHBTHxVw8Tw5hRm%2B1jNAQ%3D&reserved=0
________________________________
From: Jason Huynh <jh...@vmware.com>
Sent: Tuesday, January 11, 2022 9:35 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
+1 for this release
On 1/6/22, 9:22 AM, "Dan Smith" <da...@vmware.com> wrote:
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Agreed, I think we'll want to do another release later to pickup the latest geode and log4j. The lack of RC1 is intentional - this is creating an official release based on what was already linked from the confluent hub.
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Good catch! I created GEODE-9925 for the missing dependencies.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
Can you clarify which things are in conflict? I think the file name for geode is not a hard requirement, just a convention we picked. Also the location of LICENSE and NOTICE files - is there some confluent requirement? Apache says those files should be at the top level for a source distribution, but I'm not clear about a binary distribution. For example, our jar files put them under META-INF, which I think is the java convention.
My inclination is to continue with this release as is and create a follow up release that updates log4j and the LICENSE, NOTICE files, so I'm leaving this VOTE open in hopes of getting some more votes.
-Dan
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 4, 2022 5:13 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
As it is primarily created for Confluent Marketplace we need to follow the steps required for hosting in the marketplace, which included how things are to be named, folder structure etc.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
We can definitely add the missing licenses and wait for 1.12.8 release of Apache Geode to update those dependencies.
Regards
Naba
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Tuesday, January 4, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cdoevans%40vmware.com%7C976d5d23599d45e7ae7b08d9d564d0a5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637775451252718005%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7esXkfI%2FCep0FT9rzxhIwqMhYHnJFJcgcVcuR%2BYJ50w%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cdoevans%40vmware.com%7C976d5d23599d45e7ae7b08d9d564d0a5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637775451252718005%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Nq%2FcOCpauEGZgvDFMX93UCT%2B8hlo4OX9ZnB2rE5aIh8%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Nabarun Nag <nn...@vmware.com>.
+1 to move along with this release.
Here is the URI of the component archive specification set by Confluent[1]. Our first delivery had to be changed to meet these requirements.
Regards
Naba
[1]https://docs.confluent.io/home/connect/confluent-hub/component-archive.html
________________________________
From: Jason Huynh <jh...@vmware.com>
Sent: Tuesday, January 11, 2022 9:35 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
+1 for this release
On 1/6/22, 9:22 AM, "Dan Smith" <da...@vmware.com> wrote:
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Agreed, I think we'll want to do another release later to pickup the latest geode and log4j. The lack of RC1 is intentional - this is creating an official release based on what was already linked from the confluent hub.
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Good catch! I created GEODE-9925 for the missing dependencies.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
Can you clarify which things are in conflict? I think the file name for geode is not a hard requirement, just a convention we picked. Also the location of LICENSE and NOTICE files - is there some confluent requirement? Apache says those files should be at the top level for a source distribution, but I'm not clear about a binary distribution. For example, our jar files put them under META-INF, which I think is the java convention.
My inclination is to continue with this release as is and create a follow up release that updates log4j and the LICENSE, NOTICE files, so I'm leaving this VOTE open in hopes of getting some more votes.
-Dan
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 4, 2022 5:13 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
As it is primarily created for Confluent Marketplace we need to follow the steps required for hosting in the marketplace, which included how things are to be named, folder structure etc.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
We can definitely add the missing licenses and wait for 1.12.8 release of Apache Geode to update those dependencies.
Regards
Naba
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Tuesday, January 4, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cnnag%40vmware.com%7C6a115177ac9b453f52b408d9d528c236%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637775193312895605%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=WSa6QcLxO5rC%2FowZOHYBcgtSdF%2BbASBKxPARYh%2Bvwy4%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cnnag%40vmware.com%7C6a115177ac9b453f52b408d9d528c236%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637775193312895605%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TCHjhTG7J8ePBG5S0cujY0wR6G18M4W9VfEkfAEfKsM%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Jason Huynh <jh...@vmware.com>.
+1 for this release
On 1/6/22, 9:22 AM, "Dan Smith" <da...@vmware.com> wrote:
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Agreed, I think we'll want to do another release later to pickup the latest geode and log4j. The lack of RC1 is intentional - this is creating an official release based on what was already linked from the confluent hub.
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Good catch! I created GEODE-9925 for the missing dependencies.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
Can you clarify which things are in conflict? I think the file name for geode is not a hard requirement, just a convention we picked. Also the location of LICENSE and NOTICE files - is there some confluent requirement? Apache says those files should be at the top level for a source distribution, but I'm not clear about a binary distribution. For example, our jar files put them under META-INF, which I think is the java convention.
My inclination is to continue with this release as is and create a follow up release that updates log4j and the LICENSE, NOTICE files, so I'm leaving this VOTE open in hopes of getting some more votes.
-Dan
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 4, 2022 5:13 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
As it is primarily created for Confluent Marketplace we need to follow the steps required for hosting in the marketplace, which included how things are to be named, folder structure etc.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
We can definitely add the missing licenses and wait for 1.12.8 release of Apache Geode to update those dependencies.
Regards
Naba
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Tuesday, January 4, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cjhuynh%40vmware.com%7C1f122071bf754da6e1a708d9d1392a6e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637770865743234863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=21hMiDE0ic2UWBF%2BSWpVHntucBuyYaP2bVXI0%2BRcw2A%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cjhuynh%40vmware.com%7C1f122071bf754da6e1a708d9d1392a6e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637770865743234863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=BWDnc06%2FJt3cEA93cYD7NisPscbL27jtent22T1UEgM%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Dan Smith <da...@vmware.com>.
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Agreed, I think we'll want to do another release later to pickup the latest geode and log4j. The lack of RC1 is intentional - this is creating an official release based on what was already linked from the confluent hub.
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Good catch! I created GEODE-9925 for the missing dependencies.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
Can you clarify which things are in conflict? I think the file name for geode is not a hard requirement, just a convention we picked. Also the location of LICENSE and NOTICE files - is there some confluent requirement? Apache says those files should be at the top level for a source distribution, but I'm not clear about a binary distribution. For example, our jar files put them under META-INF, which I think is the java convention.
My inclination is to continue with this release as is and create a follow up release that updates log4j and the LICENSE, NOTICE files, so I'm leaving this VOTE open in hopes of getting some more votes.
-Dan
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Tuesday, January 4, 2022 5:13 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
As it is primarily created for Confluent Marketplace we need to follow the steps required for hosting in the marketplace, which included how things are to be named, folder structure etc.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
We can definitely add the missing licenses and wait for 1.12.8 release of Apache Geode to update those dependencies.
Regards
Naba
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Tuesday, January 4, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cdasmith%40vmware.com%7Cda7685c734334a01854f08d9cfe896aa%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637769420151268448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dC2oeeZUYR9FzMpPxNifKcdT4PZeCTJczNd1a5l4%2BmY%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cdasmith%40vmware.com%7Cda7685c734334a01854f08d9cfe896aa%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637769420151268448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=p26uItxzcZyEqFs9mxk2QgRj6kR1P6bfkNyezA64qp0%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Nabarun Nag <nn...@vmware.com>.
As it is primarily created for Confluent Marketplace we need to follow the steps required for hosting in the marketplace, which included how things are to be named, folder structure etc.
Looking at the list of things to do and conflicts with Geode / Confluent requirements. We can remove it from the Apache domain and move it to internal open source repo like gpdb or rabbitMQ while keeping the Apache License. Alternatives can be the VMware or VMware-labs opensource orgs in Github.
We can definitely add the missing licenses and wait for 1.12.8 release of Apache Geode to update those dependencies.
Regards
Naba
________________________________
From: Owen Nichols <on...@vmware.com>
Sent: Tuesday, January 4, 2022 4:45 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Cnnag%40vmware.com%7C446cbaa9b22e405c8ab908d9cfe4af60%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769403373246616%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=rIRSVkdDIlv0c2yFZDSXZe9fDFrOX0usjDtyyEDa0%2Bg%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Cnnag%40vmware.com%7C446cbaa9b22e405c8ab908d9cfe4af60%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769403373246616%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3yvWDc7u%2FNi%2FkF5zXQKDYkkEOImzOMxWnDAgFzm8P%2B4%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan
Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2
Posted by Owen Nichols <on...@vmware.com>.
Quibbles:
- artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago)
- not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later this month.
- the log4j version 2.16.0 advertised in this release fixes only 2 of the 4 recent log4j vulnerabilities. I would prefer to see log4j 2.17.1.
- vote email is missing a link to release notes and a link to the KEYS file used to sign the release.
- artifact paths and email subject are missing "RC1" qualifier
Concerns:
- NOTICE and LICENSE are found inside a "doc" folder instead of at the top level of the artifact
- Some dependencies are missing from LICENSE. While most deps are Apache2 and don't require a mention, LatencyUtils is BSD-2 and should be mentioned, and likely a few others from Geode's LICENSE need to be there as well because they are incorporated in source form into geode-core.
Please consider above suggestions for next time.
+0
On 1/4/22, 2:19 PM, "Dan Smith" <da...@vmware.com> wrote:
Hello Geode Dev Community,
This is a release candidate for Apache Geode Kafka Connector version 1.1.0.
This contains a bump to log4j 2.16.
Please do a review and give your feedback.
Voting deadline:
3PM PST Tuesday, Jan 11, 2022.
Please note that we are voting upon the source tag: rel/v1.1.0
Source and Binary Distributions: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2Fkafka-connector-1.1.0%2F&data=04%7C01%7Conichols%40vmware.com%7C371195448ed74cdb909308d9cfd033e3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769315400140534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZbgkfljvRh0McQAUL0nFvClIjW2xLq5jl8804lB7Txs%3D&reserved=0
Github: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-kafka-connector%2Ftree%2Frel%2Fv1.1.0&data=04%7C01%7Conichols%40vmware.com%7C371195448ed74cdb909308d9cfd033e3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637769315400140534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PgJv8d4yla2DjGWrppCxIFIkbwmrYT7fp2i5iBiOjNo%3D&reserved=0
Command to build the connector:
mvn package
Thanks!
-Dan