Canceled: apache/geode-native#2976 (develop - 3450bac)

Build Update for apache/geode-native - Build: #2976 Status: Canceled Duration: ? Commit: 3450bac (develop) Author: Michael Martell Message: GEODE-8836: Fix incorrect schema location for cli tests (#721) View the changeset: https://github.com/apache/geode-nati

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 differen

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

Well, I have no objection to adding a system property for this if you want to try it. Since those properties aren't technically part of the public API I don't think we need to offer full support for what happens when the setting breaks. I'm just thinking ahead to what will happen when the protoc

Re: [Proposal] Geode Native Library Versioning

** sorry for the trashed formatting originally ** I would appreciate some feedback on this proposal by the end of day Friday, February 5th, 2021. TLDR; The proposal is to formalize what has been effectively the status quo for Geode Native release in the current source form and any future binar

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

Hi Dan, Thanks a lot for your comments. The scope of the RFC is not very ambitious. As I pointed out in it, the idea is not to implement the backward compatibility of clients with older servers. Rather, the aim is to allow to take advantage of the fact that serialization or other types of chan

[Proposal] Geode Native Library Versioning

I would appreciate some feedback on this proposal by the end of day Friday, February 5th, 2021. TLDR; The proposal is to formalize what has been effectively the status quo for Geode Native release in the current source form and any future binary form. The Problem Geode Native, specifically th

Canceled: apache/geode-native#2975 (develop - c655c68)

Build Update for apache/geode-native - Build: #2975 Status: Canceled Duration: ? Commit: c655c68 (develop) Author: M. Oleske Message: Update to ace 7 (#732) Authored-by: M. Oleske View the changeset: https://github.com/apache/geode-native/compare/6391584c19

Canceled: apache/geode-native#2974 (develop - 6391584)

Build Update for apache/geode-native - Build: #2974 Status: Canceled Duration: ? Commit: 6391584 (develop) Author: Blake Bender Message: GEODE-8871: parse server response messages for PUT and CONTAINS_KEY (#730) - parse server response messages for PUT and CO

Canceled: apache/geode-native#2973 (develop - 78d2fbf)

Build Update for apache/geode-native - Build: #2973 Status: Canceled Duration: ? Commit: 78d2fbf (develop) Author: Blake Bender Message: GEODE-8887: Refactor EventIdTSS class (#733) - Use Meyers singleton pattern for global singleton (threadId), and thread l

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 optimi

Inputs for efficient querying

Hello Team, I am loading data into Geode (V 1.12) with the following *Key (of type String)* and *value (custom java object - ValueObject)*. *public class ValueObject implements Serializable {* * private int id;* * private String keyColumn; <- Region.Key * * private String

Integrating Geode with the Rapid membership service

There was an effort to modularize the membership system in Geode and I spent some time seeing if a different membership service could be integrated with Geode in place of the current implementation. I wrote a blog post about it here: https://brucesch.blogspot.com/2021/01/integrating-apache-geod