Re: Github actions - Integration tests

That ConcurrentTestRunnerTest is testing a test utility to see if it can catch race conditions. We didn't end up using that utility as much as I thought we might. You could consider just ignoring/deleting that test. -Dan From: Sai Boorlagadda Sent: Tuesday,

Re: priority list

; And as for Geode repository, considering the number of resources its CI >> requires, I'd say GH actions is a no go... >> Also, I think it was Dan Smith, the one that pointed out that Apache has >> a Jenkins instance available, so every Apache project can use its resource

Update: Geode not moving to the attic

Hi folks, I have some good news! Notifying the board mailing list of our vote to move Geode to the attic got some attention. Several inactive PMC members and some new folks from the Apache membership have expressed interest in helping with the project. With this help, we do not need to move

[DRAFT] Geode Board Report for November 9th

In addition to the resolution to terminate the geode project, I think we should file a board report for this quarter with some more details. Here is a draft, let me know what you think. ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data

Re: [RESULT] [VOTE] Move geode to the attic

, there are options to raise a community and reboot the project within the apache foundation, so this doesn't have to be the end of the line. -Dan From: Dan Smith Sent: Thursday, November 3, 2022 3:15 PM To: u...@geode.apache.org ; dev@geode.apache.org Subject: [RESULT] [VOTE] Move geode

[RESULT] [VOTE] Move geode to the attic

This vote is now closed, thanks to everyone who voted. The vote has passed with 4 binding PMC members voting to move the project to the attic. I think the next step is that I will add an item to the agenda for the next Apache board meeting for the board to consider. I'll also put the details in

Re: [VOTE] Move geode to the attic

. -Dan From: Xiaojian Zhou Sent: Sunday, October 30, 2022 10:51 PM To: u...@geode.apache.org ; dev@geode.apache.org Subject: Re: [VOTE] Move geode to the attic !! External Email Vote to move to attic. Regards Xiaojian Zhou, PMC of geode From: Dan Smith Date

Re: [VOTE] Move geode to the attic

VCI6Mn0%3D%7C3000%7C%7C%7Csdata=wo6wDQSJk8FdjjJs%2F8IM5Lnh2sn9b%2F8E2Epr3Uw9HlM%3Dreserved=0 > On Oct 24, 2022, at 10:51 AM, Dan Smith wrote: > > ⚠ External Email > > Hi folks, > > Last week we discussed moving Geode to the attic [1]. I'm sad to find us at > this

[VOTE] Move geode to the attic

Hi folks, Last week we discussed moving Geode to the attic [1]. I'm sad to find us at this point. But given that we will soon be without three active members to form a functional PMC, it's time to put this to a vote. I propose we dissolve the Geode PMC and move the Geode project to the attic.

CVE-2022-34870: Apache Geode stored Cross-Site Scripting (XSS) via data injection vulnerability in Pulse web application

Apache Geode versions up to 1.15.0 are vulnerable to a Cross-Site Scripting (XSS) via data injection when using Pulse web application to view Region entries. This issue is being tracked as GEODE-10411

CVE-2022-34870: Apache Geode stored Cross-Site Scripting (XSS) via data injection vulnerability in Pulse web application

Apache Geode versions up to 1.15.0 are vulnerable to a Cross-Site Scripting (XSS) via data injection when using Pulse web application to view Region entries. This issue is being tracked as GEODE-10411

[DISCUSS] Move geode to the attic

Hi folks, Unfortunately, it is time to consider moving Geode to the Apache attic. After VMware's announcement that it will stop contributing to Geode, we've tried in the last couple months to recruit additional contributors to continue supporting the project [1]. However, this last week there

New committer - Jakov Varenina

The Apache Geode Project Management Committee has invited Jakov Varenina to become a Geode committer and we are pleased to announce he has accepted. Please join me in welcoming Jakov! Best regards, Dan Smith on behalf of the Apache Geode PMC

Re: https://concourse.apachegeode-ci.info/ is shutting down

If github actions don't pan out, we previously ran geode CI on the apache jenkins instance. According to the instructions I should be able to grant folks access if anyone wants to try the jenkins option - https://cwiki.apache.org/confluence/display/INFRA/Jenkins -Dan

Re: [VOTE] Apache Geode 1.15.1.RC1

+1 - Ran dev-tools/release-testing/smoketest_rc.sh -Dan From: Mario Kevo Sent: Thursday, September 29, 2022 5:36 AM To: dev@geode.apache.org Subject: [VOTE] Apache Geode 1.15.1.RC1 ⚠ External Email Hello Geode Dev Community, This is a release candidate for

Re: Jira Contributors vs Committers vs "Assign User"

I also think this is a great idea if we can do it. Thanks for bringing it up, Kirk! -Dan From: Mark Bretl Sent: Thursday, September 22, 2022 10:35 AM To: dev@geode.apache.org Subject: Re: Jira Contributors vs Committers vs "Assign User" ⚠ External Email Hey

Re: Request JIRA Ticket Assgin Permission

Hi Xu Weijie, I gave you permission in JIRA, you should be able to assign that issue to yourself now. If you haven't already seen it, here is our wiki page with some helpful information about how to contribute - https://cwiki.apache.org/confluence/display/GEODE/How+to+Contribute. Thank you!

Re: [DRAFT] Apache Geode Board report due by Wed May 11th

I submitted this report to the board. Thanks! -Dan From: Dan Smith Sent: Monday, May 9, 2022 4:20 PM To: dev@geode.apache.org Subject: [DRAFT] Apache Geode Board report due by Wed May 11th Here is a draft of our board report for this quarter. Please let me know

[DRAFT] Apache Geode Board report due by Wed May 11th

Here is a draft of our board report for this quarter. Please let me know by the end of the day Tuesday if there is anything you would like me to change or add. Thanks! -Dan ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management

Re: [discuss] Future of the geode-redis module

The PRs to remove this module have been approved merged - from geode, geode-benchmarks, and geode-examples. -Dan From: Dan Smith Sent: Wednesday, May 4, 2022 2:06 PM To: dev@geode.apache.org Subject: Re: [discuss] Future of the geode-redis module Since

Re: [discuss] Future of the geode-redis module

Since it seems there is consensus to remove this module, I created this PR - https://github.com/apache/geode/pull/7657. If folks approve of this PR there will be additional PRs to geode-benchmarks and geode-examples to remove references to this module. -Dan

Re: Peer-to-peer connections use the --server-port causing the server to hang during startup

I think the membership-port-range determines the port that the server side of the TCP socket is listening on. What I see in your log statement is the port number of the client side of the socket (where it says localport=37392). The port for the client side of a socket comes from the ephemeral

Re: Geode Jira permissions

Hi Oleksii, Welcome! You should have access to the Geode JIRA now. If you haven't already you might want to check out our How to Contribute page for information on how to get started contributing to Geode. Thanks, -Dan

Re: Request access to JIRA

Hi Michael, Welcome! You should have access now. If you haven't already, you might want to check out our How to Contribute page for information on how to get started contributing to Geode. Thanks, -Dan

Re: Request for Permissions

Hi Max, Welcome! I gave you permissions to assign tickets to yourself on the geode JIRA. For submitting changes to the geode and geode-site repositories, please go ahead and file pull requests against those repos on github. You can check out our How to

Re: [Suspected Spam] [VOTE] Apache Geode 1.14.4.RC1

+1 Ran smoketest_rc.sh -Dan From: Eric Shu Sent: Tuesday, March 15, 2022 5:01 PM To: dev@geode.apache.org Subject: Re: [Suspected Spam] [VOTE] Apache Geode 1.14.4.RC1 +1 Run end to end test cases against the build without seeing new issues.

Re: [Suspected Spam] [VOTE] Apache Geode 1.13.8.RC1

+1 - ran smoketest_rc.sh -Dan From: Nabarun Nag Sent: Tuesday, March 15, 2022 9:55 AM To: dev@geode.apache.org Subject: Re: [Suspected Spam] [VOTE] Apache Geode 1.13.8.RC1 +1 based on pipeline status of the artifacts Regards Naba

Re: [Suspected Spam] [VOTE] Apache Geode 1.12.9.RC1

+1 * Ran smoketest_rc - https://github.com/apache/geode/tree/develop/dev-tools/release-testing * verified concourse build passed * looked at artifacts From: Donal Evans Sent: Wednesday, March 9, 2022 9:04 AM To: dev@geode.apache.org Subject: Re:

Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

s and have documentation for mitigation might be a better approach. My $.02 --Mark On Fri, Feb 4, 2022 at 11:34 AM Dan Smith wrote: > Counting the kafka connector I'm not sure bragging about CVE patching > speed is justified, but otherwise looks good to me!

[DISCUSS] Testing and voting on release candidates

Hi all, I'd like to suggest something that might make voting on releases a little clearer and easier. I feel like we've been a bit vague about what kind of testing PMC members are supposed to do on a release candidate, and I see different folks (including myself) running different kinds of ad

Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

Counting the kafka connector I'm not sure bragging about CVE patching speed is justified, but otherwise looks good to me! -Dan From: Nabarun Nag Sent: Tuesday, February 1, 2022 2:25 PM To: dev@geode.apache.org Subject: Re: [DRAFT] Apache Geode Board report due

Re: Changes to Public API Return Only Interfaces

> When a public API interfaces has no use case where 3rd parties would > implement, such as return types or factory allocated implementations, there > should not be a compile time breaking change. In the case of IndexStatistics > there is no use case where a 3rd party could implement and

[ANNOUNCE] Apache Geode Kafka Connector 1.1.0

/releases/ We would like to thank all the contributors that made the release possible. Regards, Dan Smith on behalf of the Apache Geode team

[ANNOUNCE] Apache Geode Kafka Connector 1.1.0

/closer.lua/geode/kafka-connector-1.1.0 We would like to thank all the contributors that made the release possible. Regards, Dan Smith on behalf of the Apache Geode team

Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2

=%2BpkOe5bQQInlr9yMtrrWI9rhBR9RUkg7YHdZVjiLn%2Fw%3Dreserved=0 From: Jason Huynh Sent: Tuesday, January 11, 2022 9:35 AM To: dev@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&qu

Re: Please add me to the geode community

Hi Nianesh, You should be able to join this mailing list by sending an email to dev-subscr...@geode.apache.org. You may also want to subscribe to the user mailing list - user-subscr...@geode.apache.org. Thanks! -Dan From: Nainesh Jhaveri Sent: Thursday,

Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2

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" wrote: Hello Geode Dev Community, This is a release candidate for Apache Geode Kafka

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 wrote: This is related to the earlier discussion about the kafka connector. This code was already linked

[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

Re: [DISCUSS] proposal to pare down old-version testing

Looking at KnownVersion.java - we did make protocol changes in 1.12.1 and 1.13.2. So, my suggestion would be to keep 1.12.0 and 1.13.1, but dop all the other patch versions that aren't the latest. -Dan From: Dan Smith Sent: Monday, January 3, 2022 10:37 AM

Re: [DISCUSS] proposal to pare down old-version testing

+1 - this seems reasonable to me. If we do make a protocol change in a patch, we could potentially keep around an older patch version just in that specific case, but otherwise I think this makes sense. -Dan From: Anthony Baker Sent: Thursday, December 23, 2021

Re: [VOTE] - Apache Geode Kafka Connector 1.1.0

Well, I haven't seen any votes on this and it's almost Christmas. Let's table this until next year and I'll send out another vote email. -Dan On Dec 16, 2021 11:33 AM, Dan Smith wrote: This is related to the earlier discussion about the kafka connector. This code was already linked from

Re: [VOTE] - Apache Geode Kafka Connector 1.1.0

/release-policy.html. -Dan From: Dan Smith Sent: Thursday, December 16, 2021 11:25 AM To: dev@geode.apache.org Subject: [VOTE] - Apache Geode Kafka Connector 1.1.0 Hello Geode Dev Community, This is a release candidate for Apache Geode Kafka Connector version

[VOTE] - Apache Geode Kafka Connector 1.1.0

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, including the checks you performed. Voting deadline: 3PM PST Monday, December 20 2021. Please note that we are

Re: ANNOUNCE : Apache Geode Kafka Connector v1.1.0

Hi Naba, Thanks for patching log4j in the kafka connector! However, I think we should be following the official apache release policy [1] for this connector, which means a VOTE requiring 3 PMC signatures, signed artifacts, releasing the artifacts first on the apache downloads site, etc. In

Re: [Suspected Spam] [VOTE] Apache Geode 1.13.6.RC1

+1 Ran geode-release check to build from source and validate signatures on my machine. I looked into the 1.13 pipeline failure in the upgrade-test-openjdk11 job. I think the tests are failing due to resource issues - we see messages about missing heartbeats, etc. Ordinarily I would say we

Re: [VOTE] Apache Geode 1.14.2.RC1

+1 to 1.14.2.RC1 Ran geode-release check to build from source and verify signatures on my machine. -Dan From: Nabarun Nag Sent: Wednesday, December 15, 2021 11:00 AM To: dev@geode.apache.org Subject: Re: [VOTE] Apache Geode 1.14.2.RC1 +1 to 1.14.2.RC1 *

Re: [Suspected Spam] [VOTE] Apache Geode 1.12.7.RC1

+1 Ran geode release check to validate sigs and build from source on my own machine. -Dan From: Owen Nichols Sent: Tuesday, December 14, 2021 6:19 PM To: dev@geode.apache.org Subject: [Suspected Spam] [VOTE] Apache Geode 1.12.7.RC1 Hello Geode Dev Community,

Re: Question related to orphaned .drf files in disk-store

9b408cd8f%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637738772194852171%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=nA%2FNGaOEg1sR8yYpRUHkhfupciFhhMfwiPyhGv%2BSHnw%3D=0> BRs/Jakov On 24. 11. 2021. 23:12, Dan Smith wrote: The .drf file contains des

Re: Client terminating when trying to connect to an SSL configured locator

I guess the alternative would be for the client to automatically switch to SSL if it detected the server was using SSL? It is not currently doing that, as you discovered. That might be a nice feature to have to support upgrading to SSL. At some point, it is important for users that want SSL to

Re: Question related to orphaned .drf files in disk-store

The .drf file contains destroy records for entries in any older oplog. So even if the corresponding .crf file has been deleted, the .drf file with the same number still needs to be retained until the older .crf files are all deleted. 7680 does seem like a lot of oplogs. That data structure is

Re: API check error when adding a new method to a public interface

First off, it's not reasonable to say that we will not add any new methods to the public API unless we release a new major version. We will continue to add methods to the public API, which is something we've been doing in pretty much every minor version. Our practice has been to make sure that

Re: Added to Jira

Done! You should have access now. -Dan From: Kristen Oduca Sent: Tuesday, November 16, 2021 4:03 PM To: dev@geode.apache.org Subject: Added to Jira Hi, Can I be added to the Geode Jira so I can assign myself tasks? My username is kris10. Thanks, Kristen

[DRAFT] Geode Board Report due by Wednesday Nov 10th

This is a draft of our report to the board. I will submit it by 5PM Thursday if no one objects. Please let me know if there are details you'd like me to add! -Dan ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that

Re: [VOTE] Apache Geode 1.12.5.RC1

+1 to 1.12.5.RC4. Reviewed changes, geode-release-check. -Dan From: Dave Barnes Sent: Thursday, October 21, 2021 3:30 PM To: dev@geode.apache.org Subject: [Suspected Spam] Re: [VOTE] Apache Geode 1.12.5.RC1 +1 docs check out: javadocs, user guide (manual

Re: Region is not created on one of the servers

have some backup to rollback cluster configuration. Also, this can happen for all commands that editing cluster configuration. It looks like this is not designed to execute some commands in parallel with starting servers. BR, Mario ____ Šalje: Dan Smith Poslano: 8.

Re: Geode-9621: Spotless overstepping its boundary of formatter

>The formatter now throws when there is a naked version-string on the >dependency line, as we discussed. This new behavior seems reasonable to me. And I think this is what you are asking for, Udo? I do agree that spotlessApply shouldn't change any behavior and cause someone to lose part of

Re: Region is not created on one of the servers

This seems like something ought to work, so I would call it a bug if the region didn't get created on 1 server. At first glance, it looks like the problem is that we distribute the region to all the servers before adding it to cluster config? Seems like we need to do distribution after​ adding

Re: [DISCUSS] Upgrading to Lucene 7.1.0

My understanding from our previous discussion about upgrading lucene was that we talked about pausing the asynchronous indexing process during the rolling upgrade. I don't remember a discussion that it was ok to not allow queries during the upgrade. But this is what we added to the docs: "All

Re: [DISCUSS] Upgrading to Lucene 7.1.0

Does anyone have more context on why lucene queries won't work during the rolling upgrade? I can see what added a line to the documentation and changed the tests not to do queries, but I'm not sure why we needed to do that. -Dan From: nabarun nag Sent: Monday,

Re: [DISCUSS] Remove geode-dotnet-core-client repo

, and keeping the two repos in sync would be untenable or at least very difficult. Thus geode-dotnet-core-client is not in use and never really was, actively. Thanks, Blake -Original Message- From: Dan Smith Sent: Thursday, September 2, 2021 9:18 AM To: dev@geode.apache.org Subject: [DISCUSS

Re: testing Geode Net Core

It does look like maybe you are trying to use the geode-dotnet-core-client repository, which is stale. There is a separate thread ongoing to delete that repo. The net-core client work is now happening in the geode-native repo, which doesn't have this hardcoded c:/Users/bblake/ path! -Dan

[DISCUSS] Remove geode-dotnet-core-client repo

It looks like the geode-dotnet-core-client repository is stale, and the code has moved to the geode-native repository. Is it ok to go ahead and remove the geode-dotnet-core-client repository? If so, I'll figure out how to make that happen. At a minimum we could commit a change that deletes all

Re: Request JIRA contributor permissions

You should have permissions now. Welcome! -Dan From: Eric Zoerner Sent: Wednesday, September 1, 2021 4:49 PM To: dev@geode.apache.org Subject: Request JIRA contributor permissions I am a new developer on the Geode project and need permissions to assign tickets

Re: [VOTE] Apache Geode 1.14.0.RC2

+1 -Dan From: nabarun nag Sent: Tuesday, August 31, 2021 5:36 PM To: dev@geode.apache.org Subject: [VOTE] Apache Geode 1.14.0.RC2 Hello Geode Dev Community, This is a release candidate for Apache Geode version 1.14.0.RC2. Thanks to all the community members

[DISCUSS] Integrate Geode's redis API with the security manager

Hi folks, Here's a small RFC related to using the security manager with our redis API. Comments welcome, here or on the wiki. https://cwiki.apache.org/confluence/display/GEODE/Integrate+Geode%27s+redis+API+with+the+security+manager Thanks! -Dan

Re: [DRAFT] Geode Board Report due by Wed Aug 11st

Board report has been submitted. Thanks! -Dan From: Dan Smith Sent: Tuesday, August 10, 2021 11:29 AM To: dev@geode.apache.org Subject: [DRAFT] Geode Board Report due by Wed Aug 11st This is a draft of the report to be submitted tomorrow -- please send me your

[DRAFT] Geode Board Report due by Wed Aug 11st

2016-11-15 (over 5 years ago) There are currently 115 committers and 54 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Dan Smith replaced Karen Miller as PMC chair on 2021-05-20 - Alberto Bustamante Reyes was added as committer on 2021-05-14

Re: Annual branch cleanup Aug 17

Would it be ok to leave the feature/redis-performance-testing branch for the time being? That is a shared branch that is being used by several people. Thanks, -Dan From: Owen Nichols Sent: Sunday, August 1, 2021 1:01 AM To: dev@geode.apache.org Subject: Annual

Re: Volunteers to be JIRA/confluence/mailing list admins?

Mn0%3D%7C1000sdata=aNHhzAdYJfY2h3X2Wj8CzdKuqjL4HLPF3QE2%2FgYKYPQ%3Dreserved=0> ____ De: Dan Smith Enviado: Wednesday, July 28, 2021 7:52:23 PM Para: dev@geode.apache.org Asunto: Volunteers to be JIRA/confluence/mailing list admins? Hi all, We have a couple of

Volunteers to be JIRA/confluence/mailing list admins?

Hi all, We have a couple of admin/human spam filter jobs that I think could use a few more volunteers. * Confluence/JIRA admins - we have a process where we grant permission to these resources to anyone who asks for access on the mailing list. This could be any committer, or really any

Re: Permissions to comment on RFCs?

is "mario.salazar.de.torres" Thanks, Mario. ____ From: Dan Smith Sent: Tuesday, July 27, 2021 11:52 PM To: dev@geode.apache.org Subject: Re: Permissions to comment on RFCs? You do need permissions. What is your confluence username? If you don't have one you

Re: Permissions to comment on RFCs?

You do need permissions. What is your confluence username? If you don't have one you can create account. Then we can add you to the Geode project (we add anyone who asks :). -Dan From: Mario Salazar de Torres Sent: Tuesday, July 27, 2021 2:10 AM To:

Re: [Suspected Spam] Re: [VOTE] Apache Geode 1.12.4.RC1

+1 Looks good to me. -Dan From: Dave Barnes Sent: Thursday, July 22, 2021 12:38 PM To: dev@geode.apache.org Subject: [Suspected Spam] Re: [VOTE] Apache Geode 1.12.4.RC1 +1 for geode docs - Checked API docs (javadocs) for correct version in page headers -

Re: [VOTE] Apache Geode 1.13.3.RC1

+1 -Dan On Jun 21, 2021 2:23 PM, Nabarun Nag wrote: +1 based on the following: * build from source * running gfsh * starting 2 site WAN cluster * verifying data propagation from the 2 sites using puts and gets * Rolling clusters from 1.12 to the release candidate. *

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

I'm also -0 on this one. I personally kinda like having the merge button disabled on my PRs until all the checks are passing so I don't have to think as much, and I'm not sure this problem is going to come up again soon. But I'm willing go with disabling it. -Dan

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

Would it be possible to just split that test up into multiple classes? It sounds like the issue is that there is so many flaky tests in that class that you can't fix them all in one PR, which might indicate it's too big. If we can't get StressNewTest to pass - that means our builds are failing

Re: Stats deprecations?

Looks like those methods were deprecated in GEODE-6850. If I'm reading that correctly, there is no reason not to change the calls to incLong, getLong, etc. I'd say go for it. -Dan From: Mark Hanson Sent: Wednesday, April 14, 2021 3:43 PM To:

Re: [DISCUSS] Monthly, synchronous community meetings

Seems like a good idea. I have no preference on video conference platform. -Dan From: Alberto Gomez Sent: Friday, April 9, 2021 1:25 AM To: dev@geode.apache.org Subject: Re: [DISCUSS] Monthly, synchronous community meetings Hi, This idea sounds great to me.

Re: [DISCUSS] removal of experimental Protobuf client/server interface

to the library, but many are maintained separately. Having a well-defined protocol for Geode is the first step in making that possible. --Jens On 3/24/21, 1:11 PM, "Dan Smith" wrote: I also worked on the protobuf interface for a little while,

Re: [DISCUSS] removal of experimental Protobuf client/server interface

I also worked on the protobuf interface for a little while, although not for as long as some of the other folks commenting. I'm ok with removing it. I do see some value in leaving stalled/incomplete projects around as bait for future developers to pick up - that seems to have worked for redis

Re: [Suspected Spam] RE: [VOTE] Apache Geode 1.13.2.RC1

+1 Ran geode-release-check against this RC, looks good to me. -Dan From: Mark Hanson Sent: Tuesday, March 16, 2021 11:02 AM To: dev@geode.apache.org Subject: Re: [Suspected Spam] RE: [VOTE] Apache Geode 1.13.2.RC1 +1 for release. Fixed a spelling error in

Re: Cached regions are not synchronized after restore

The java client at least should automatically drop its cache when it loses and restores connectivity to all the servers. See

Re: [DISCUSS] client/server communications and versioning

Ha, I was thinking of suggesting this when I saw Alberto's earlier proposal. This does seem like a good idea to only bump the client version when the protocol actually changes. One concern is that it might not be obvious that changing a DataSerializableFixedId will change the client protocol.

Re: [Proposal] Geode Native Library Versioning

ABI compatibility with the java layer has come up before [1]. At the time we decided to keep binary compatibility for the Java code. That said, it's not common to break binary without breaking source compatibility in Java. C++ is a different animal, so I can see wanting to do something

Re: [DISCUSS] RFC - Add option to allow newer Geode clients to connect to older Geode servers

From: Dan Smith Sent: Friday, January 29, 2021 1:56 AM To: dev@geode.apache.org Subject: Re: [DISCUSS] RFC - Add option to allow newer Geode clients to connect to older Geode servers I think just sending the old version will only work until we actually make any changes

Re: Inputs for efficient querying

For the best performance, you should store column2 as a java Map instead of a String which contains a json document. If column2 was Map, you could do a query like this: SELECT * FROM /exampleRegion r WHERE r.column2['k1'] IN SET('v10', 'v15', 'v7')" You can create an index on the map to

Re: [DISCUSS] RFC - Add option to allow newer Geode clients to connect to older Geode servers

I think just sending the old version will only work until we actually make any changes to the protocol. Once we do, serialization will break unless we also change the client to pretend to be that old version, including the way it serializes and deserializes messages. With this proposal there

Re: Different binding addresses for traffic & membership

I've been looking into the code a little bit to see if this is possible. I'm not sure it is right now. Here's some pointers at where to look at. Most of the magic is happening in JGroupsMessenger. JGroupsMessenger wraps jgroups, which we are using to UDP messaging related to membership. The

Re: Request for rights to write comments on Apache Geode Confluence

Done. You should have access now. Thanks! -Dan From: Jakov Varenina Sent: Monday, January 11, 2021 2:09 AM To: dev@geode.apache.org Subject: Request for rights to write comments on Apache Geode Confluence Hi devs, Could you please give me rights to write

Re: [DISCUSS] Adding CODEOWNERS to Apache Geode

Hi Owen, Thanks for pushing this forward! Given that a lot of folks are on holiday - maybe sometime in January might be a better time to merge this to develop to give everyone a chance to look at it? How about Jan 8th? I'm glad you nominated some folks to be owners by filling them in. I don't

Re: [Proposal] - Cleanup Protocol Version Checks

> Feedback appreciated by 12/18 before a formal acceptance vote is requested. BTW, I don't think a vote is necessary. If you don't get objections by 12/18 I think you can just move forward. -Dan From: Dan Smith Sent: Wednesday, December 9, 2020 11:16 AM To:

Re: [PROPOSAL] Change the default value of conserve-sockets to false

I will go ahead and withdraw my objection to this change. Based on some side conversations, at least at VMWare it sounds like we don't have customers that are not setting this flag. So the scenario I'm worried about where a customer upgrades their production cluster and has it crash due to this

Re: [Proposal] - Cleanup Protocol Version Checks

+1 to rejecting clients (and WAN sites) with versions less than KnownVersion.GFE_82, and obsolete compatibility code. -Dan From: Jacob Barrett Sent: Wednesday, December 9, 2020 9:35 AM To: dev@geode.apache.org Subject: Re: [Proposal] - Cleanup Protocol Version

Concourse TLS cert has expired

If I go to https://concourse.apachegeode-ci.info/ I get this error - who can fix this? The certificate for concourse.apachegeode-ci.info expired on 12/2/2020. -Dan

[DISCUSS] - Use Java 11 for geode-examples

A contributor submitted a PR[1] to our geode examples project that uses Java 11 APIs. It doesn't pass travis because we're still building the examples with Java 8. I think it might be reasonable to switch the minimum java version of the examples to Java 11. If there are no objections, I'll go

Re: [PROPOSAL] Change the default value of conserve-sockets to false

Personally, this has caused enough grief in the past (both ways, actually!) that I 'd say this is a major version change. I agree with John. Either value of conserve-sockets can crash or hang your system depending on your use case. If this was just a matter of slowing down or speeding up

Re: Request for Jira Permissions

Done. You should have access now. -Dan From: John Hutchison Sent: Wednesday, November 18, 2020 11:00 AM To: dev@geode.apache.org Subject: Request for Jira Permissions Hi, I’d like to request permission to assign jira tickets to myself and also to reopen

Re: [VOTE] Apache Geode 1.13.1.RC2

+1 Looks good to me! I ran the geode-release-check against it, looked for binary artifacts, checked the pipeline. -Dan From: Dick Cavender Sent: Thursday, November 12, 2020 5:00 PM To: dev@geode.apache.org Subject: [VOTE] Apache Geode 1.13.1.RC2 Hello Geode

Re: Apache Geode 1.13.1 patch proposal

+1 sounds great! From: Dick Cavender Sent: Thursday, November 12, 2020 10:59 AM To: dev@geode.apache.org Subject: Apache Geode 1.13.1 patch proposal It's been two months since the 1.13.0 release and there have been 28 important fixes on support/1.13 that the

  1   2   3   4   5   6   7   8   9   >