Geode versions

Hello, Where can I find information on up-coming GEODE versions, release dates etc.? The last released version I know if is 1.1.1, There is already a reference for 1.2 in the release notes here: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes Also, reference for 1.3 here: https:/

GEODE and GEODE-native compatibility

Hi, I am using both the GEODE and GEODE native libraries, and since the native library has no numbered version I am wondering if there are any compatibility issues. Will the native library work with versions 1.0.0 and 1.1.1 seamlessly? Thanks, Roi This message and the information contained h

RE: Geode versions

, We have cut a release branch for 1.2.0. Once we have fixed the remaining bugs we will vote on releasing. We don’t published expected release dates but I expect that it won’t be too much longer. Thanks, Anthony > On Jun 5, 2017, at 2:49 AM, Roi Apelker wrote: > > Hello, > &

RE: GEODE and GEODE-native compatibility

I'll send the same answer. There have been no official Geode release of Geode Native but the current development branch is known to work with Geode server 1.0 and 1.1. -Jake Sent from my iPhone > On Jun 5, 2017, at 2:49 AM, Roi Apelker wrote: > > Hi, > > I am using

Question regarding the next release

Hi, Is there an expected date for release of 1.2? Are there any backward compatibility issues in this version? If so, are they documented separately from the other issues? Thanks, Roi This message and the information contained herein is proprietary and confidential and subject to the Amdocs p

Question regarding node failure scenario

Hi, I have the following scenario, I wonder if anyone can comment on it - is it a known issue, maybe it was solved already in later version, etc. (I am using version 1.0.0) Bear with me I am a bit new here :) I have a replicated Node, say N1 and its replicated N2 (N2 gets activated when N1 is

Geode "minor minor" versions

Hi, I understood from previous discussions, that apart from version 1.3 there are no other foreseeable versions in the future. * What about "minor minor" versions - 1.1.2? 1.2.1? - what is the "trigger" for such versions? * Are fixes being released as well? Or is it just that

RE: Geode "minor minor" versions

u are new to our community? Updates get triggered as needed whenever there is an important bug to fix and/or foundational changes that need to be brought to production, even if they don't create new features right away. On Tue, Jul 4, 2017 at 4:56 AM, Roi Apelker wrote: > Hi, > > I

Question regarding node failure scenario

Hi, (Bear with me I am a bit new here :)) I have the following scenario, I wonder if anyone can comment on it - is it a known issue, maybe it was solved already in later version, etc. (I am using version 1.0.0) Or maybe you can point me to somewhere in the code. I have posted this question once

RE: Question regarding node failure scenario

t; <https://plus.google.com/+Pivotal> [image: youtube] > <https://www.youtube.com/playlist?list=PLAdzTan_eSPScpj2J50ErtzR9ANSzv > 3kl> > > > 2017-07-23 22:04 GMT+09:00 Roi Apelker : > > > Hi, (Bear with me I am a bit new here :)) > > > > I have the fol

continuous query internal mechanism

Hello, I am trying to look into the code of the continuous query mechanism - where the GEODE server sends the notification back to the client. Can anyone point me to the central classes of continuous query, especially to the one that is responsible for the calculation of the new data and packin

RE: continuous query internal mechanism

continuous query internal mechanism You can find those in CqServiceImpl.process*()... -Anil. On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker wrote: > Hello, > > I am trying to look into the code of the continuous query mechanism - > where the GEODE server sends the notification back

RE: continuous query internal mechanism

ClientUpdateMessageImpl and CacheClientUpdater (for client side processing). -Anil. On Mon, Aug 7, 2017 at 11:01 AM, Roi Apelker wrote: > Thanks, > > By the way, is there any difference in the behaviour of the server, if > the client that registered the CQ is a native (C++) client? > >

RE: continuous query internal mechanism

"region.registerInterest(*)". And CqEvents are for CQs registered. -Anil. On Tue, Aug 8, 2017 at 12:27 AM, Roi Apelker wrote: > Shukriya > > What is the difference between registered events and CQ events? > > -Original Message- > From: Anilkumar Gingade [mailto:aging..

continuous query internal mechanism questions

MemberCrashedEvent (maybe due to some other error), and that the CQ notifications are received normally. Can anyone clear things up for me? Any comment on any of the statements above will be greatly appreciated. Thanks, Roi -Original Message- From: Roi Apelker Sent: Wednesday, August 09, 2017 3:21

continuous query - high availability and assurance

Hi, I have been working on an issue related to continuous query mechanism, and I would like to know if this mechanism, with High availability, assures 100% data integrity? For example, if I have 2 nodes where a client registered to CQ, and one node fails, is there any scenario, in which a noti

RE: continuous query internal mechanism questions

age). > > It seems the extra ExecuteCQ message failing and then closing the cq > might be putting the system in a weird state... > > On Tue, Aug 15, 2017 at 7:56 AM Roi Apelker > wrote: > > > Hi, > > > > I have been examining the continuous query registration

RE: continuous query internal mechanism questions

putting the system in a weird state... On Tue, Aug 15, 2017 at 7:56 AM Roi Apelker wrote: > Hi, > > I have been examining the continuous query registration mechanism for > quite some time This is related to an issue that I have, where > sometimes a node crashes (1 node out of 2)

eviction files

Hi, I am looking into the internals of the eviction process, Can anyone point me to the most important classes, the main mechanism "wheels" etc.? Thanks, Roi -Original Message----- From: Roi Apelker Sent: Wednesday, August 16, 2017 8:38 PM To: dev@geode.apache.org S

Indxes and hints

in, I am looking to overcome the situation, where as it seems, the records are loaded unnecessarily from disk) Thank you, Roi -Original Message- From: Roi Apelker Sent: Thursday, August 24, 2017 7:03 PM To: dev@geode.apache.org Subject: eviction files Hi, I am looking into the

Query mechanism

Hi, I am looking into the internals of how the query process works, and how indexes/hints affect it, Can anyone point me to the most important classes, the main mechanism "wheels" etc.? Thanks, Roi -Original Message----- From: Roi Apelker Sent: Sunday, August 27, 2017 1

RE: Indxes and hints

can be defined on fields in the value. It will work the same. If you are sure you are already using an index in the query and still loading every value for every execution of that query, there may be something weird going on... On Sun, Aug 27, 2017 at 2:55 AM Roi Apelker wrote: This

RE: Indxes and hints

use a hint on a, or a hint on b, or a hint on both, it will first do a select on the hinted, and ONLY THEN the others? Can anyone refer me to the code (where the 2 phase search occurs)? Where is the value finally loaded from disk? Thank you Roi -Original Message- From: Roi Apelker S

RE: Indxes and hints

Store.getTargetObject. On Wed, Aug 30, 2017 at 9:21 AM Roi Apelker wrote: > One more question: > > As I am trying to create a situation where the disk is accessed as > least as possible (with a select distinct from X where a=1 and b>10 > and c=true; In which a and b are in

RE: continuous query internal mechanism questions

at 7:56 AM Roi Apelker wrote: > Hi, > > I have been examining the continuous query registration mechanism for > quite some time This is related to an issue that I have, where > sometimes a node crashes (1 node out of 2), and the other one does not > send CQ events. The CQ is

GEODE 1.2 and java 8

Hi, As we have moved to Java 8, and compiled GEODE 1.2 with it, Are there any recommendations regarding java parameters (JVM or any other) that can be suggested? Thanks Roi This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy state

Query mechanism

Hi, Is there a design document which explains the query mechanism? Main classes, modules, main algorithm? I have been looking into this area (since I have a performance issue, where it seems that data is loaded from disk prematurely in eviction state, which causes the system to become really s

geode and open JDK / newer version of java

Hi, Has anyone tried to operate GEODE with open JDK - any version - rather than Oracle's JDK? Has anyone tried to operate GEODE with open JDK - specifically version 9 (released Sep 21 2017)? What about Oracle's version 9? Any migration issues, problems etc. ? Thanks, Roi This message and th

RE: geode and open JDK / newer version of java

e official release. --Jens On Wed, Oct 18, 2017 at 2:51 AM, Roi Apelker wrote: > Hi, > > Has anyone tried to operate GEODE with open JDK - any version - rather > than Oracle's JDK? > > Has anyone tried to operate GEODE with open JDK - specifically version > 9 (released S