Re: Queries on key fields

2018-10-15 Thread Jason Huynh
Hello Siby, I think we should keep this conversation based on Geode if possible. I think GemFire has their own support channels that you might be able to contact for help specific to GemFire... As for the commit conflicts, I assume you are using transactions? Also, I am not aware of a specific M

Re: Queries on key fields

2018-10-15 Thread anjana_nair
Jason, We are using the Map feature of GemFire and update throws CommitComflict exceptions when the same key is updated from multiple places at the same time, how can this be resolved ? This happens only at high contention though. We are retrying , but still even after a couple of retries it does

Re: Queries on key fields

2018-10-14 Thread anjana_nair
thank you that clarifieded my queries. -- Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/

Re: Queries on key fields

2018-10-09 Thread Jason Huynh
Pdx and indexing are different altogether. Pdx affects the serialization of the object. Indexing affects querying speed. Together, they should improve the entire query speed because querying can cause deserializations. With Pdx it should speed up look ups by not causing full deserialization per

Re: Queries on key fields

2018-10-09 Thread anjana_nair
is there an advantage of using one vs other index on a field vs PDX serialization as both are used in query execution. -- Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/

Re: Queries on key fields

2018-10-05 Thread anjana_nair
Jason, how can we use both together, isnt it redundant as both serve the same purpose ? making retrieval faster ? -- Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/

Re: Queries on key fields

2018-10-02 Thread Jason Huynh
The index and pdx serialization are orthogonal. You will be able to use both together On Tue, Oct 2, 2018 at 10:50 AM siby_sekar wrote: > Thank you Jason that was really helpful. > > Can we use index and PDXSerialization together on a field. Here in this > case > we will be searching by session

Re: Queries on key fields

2018-10-02 Thread siby_sekar
Thank you Jason that was really helpful. Can we use index and PDXSerialization together on a field. Here in this case we will be searching by sessionId, but should we assign just PDxSerialization or index or can we use both on sessionId ? thanks, Siby. -- Sent from: http://apache-geode-incuba

Re: Queries on key fields

2018-10-01 Thread Jason Huynh
I think if you embed the sessionId into your value object and create an index, that should perform better. I am assuming if you embed the sesionId that you would then be doing queries more similar to sessionId = X or sessionId like sessionId%. Being able to use the index will prevent the query en

Re: Queries on key fields

2018-09-29 Thread siby_sekar
for us sessionId is not the actual key field. It will be something like some arbitrarystring+sessionid and we will be running queries with - like "%sessionId%" to find all entries having a particular sessionid. In this case to improve performance can we apply any index ? is this approach bet

Re: Queries on key fields

2018-09-29 Thread siby_sekar
Thank you. I have more queries on the topic. we will be applying queries like 1. key like "%sessionID% as sessionid will not be the actual key. we will have several objects where same sessionid is going to be part of multiple objects and we will have to get all objects that contains a partic

Re: Queries on key fields

2018-09-28 Thread Michael Stolz
Usually key fields are faster -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 On Fri, Sep 28, 2018 at 2:49 PM siby_sekar wrote: > Which is more performant running queries on key fields or non key fields? > > we have an object in the form > > sessionid : { List