Re: Geode - store and query JSON documents

Hi Anil, Thanks a lot for your reply. This really helps to proceed. The query shared by you worked but I need a slight variation of it, i.e where clause contains col2 (data.col2.k21 = '22') which is array unlike col1 (object). FYI: value is stored in cache. PDX[28847624, __GEMFIRE_JSON]{

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

Udo, you’re correct that individual servers can set the property independently. I was assuming this is more like the ’security-manager` property and others that require all cluster members to be in agreement. I’m not sure I understand the use case to allow this setting to be per-member. That

Re: Geode - store and query JSON documents

Ankit, Here is how you can query your JSON object. String queryStr = "SELECT d.col1 FROM /JsonRegion v, v.data d where d.col1.k11 = 'aaa'"; As replied earlier; the data is stored as PdxInstance type in the cache. In the PdxInstance, the data is stored as top level or nested collection of

Geode - store and query JSON documents

Hello geode-dev, I am *evaluating usage of Geode (1.12) with storing JSON documents and querying the same*. I am able to store the json records successfully in geode but seeking guidance on how to query them. More details on code and sample json is, *Sample client-code* import

Geode - store and query JSON documents

Hello geode-dev, I am *evaluating usage of Geode (1.12) with storing JSON documents and querying the same*. I am able to store the json records successfully in geode but seeking guidance on how to query them. More details on code and sample json is, *Sample client-code* import

Re: Geode - store and query JSON documents

Ankit: Anil can provide you some sample code of OQL query on JSON. I will find some lucene sample code on JSON for you. Regards Xiaojian On 11/23/20, 9:27 AM, "ankit Soni" wrote: Hi I am looking for any means of querying (OQL/Lucene/API etc..?) this stored data. Looking for

Re: Geode - store and query JSON documents

Hi I am looking for any means of querying (OQL/Lucene/API etc..?) this stored data. Looking for achieving this functionality first and second, in a performant way. I shared the OQL like syntax, to share my use-case easily and based on some reference found on doc. I am ok if a Lucene query or some

Re: Requests taking too long if one member of the cluster fails

Yes, lowering the member timeout is one approach I’ve seen taken for applications that demand ultra low latency. These workloads need to provide not just low “average” or even p99 latency, but put a hard limit on the max value. When you do this you need to ensure coherency across at all

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

Passed dunit tests is not enough. It might only mean we don't have enough test coverage. We need to inspect the code to see what will be the behavior when 2 servers configured different conserve-sockets. On 11/20/20, 3:30 PM, "Donal Evans" wrote: Regarding behaviour during

Re: Geode - store and query JSON documents

Anil: The syntax is OQL. But I understand they want to query JSON object base on the criteria. On 11/23/20, 9:08 AM, "Anilkumar Gingade" wrote: Gester, Looking at the sample query, I Believe Ankit is asking about OQL query not Lucene... -Anil. On 11/23/20, 9:02 AM, "Xiaojian

Re: Geode - store and query JSON documents

Gester, Looking at the sample query, I Believe Ankit is asking about OQL query not Lucene... -Anil. On 11/23/20, 9:02 AM, "Xiaojian Zhou" wrote: Ankit: Geode provided lucene query on json field. Your query can be supported.

Re: Geode - store and query JSON documents

Ankit: Geode provided lucene query on json field. Your query can be supported. https://gemfire.docs.pivotal.io/910/geode/tools_modules/lucene_integration.html However in above document, it did not provided a query example on JSON object. I can give you some sample code to query on JSON.

Re: Requests taking too long if one member of the cluster fails

On the native side of things I would suggest trying the same test with a Java client and compare. It is very possible the C++ client is lacking in its ability to respond to failures as timely as the more heavily used Java client. -Jake On Nov 23, 2020, at 3:54 AM, Mario Salazar de Torres

Re: Requests taking too long if one member of the cluster fails

Hi @John Blum, I am grateful for your explanation. Really, thanks! It has been an instructive read. Finally understood why if you allow to write on all the replicas you'll end up risking the consistency. Consequently, understood that, as in life itself, for distributed