== should in theory be faster. The compiled like eventually boils down to
a >= query but it takes a few steps to get there.
If I understand correctly. the second approach would be indexed on a string
field and the query would look similar to "select * from /region where
stringField = 'ABC'" If that is the case, I would think the == would be
faster (but that's just a guess, it might be worth it to try both and see
what the actual times are, especially with your data set)
On Wed, Nov 28, 2018 at 10:43 AM anjana_nair <siby_sek...@hotmail.com>
wrote:
> Thank you Jason.
>
> I have one more question related to this.
>
> I have two options / object structures for storing and retrieving objects.
>
> First one .
>
> Storing objects like : {key :"ConstantString_randomString", List<Objects>
> objects}
> and then use queries with like "ConstantString_%" where function index is
> applied on key field.
>
> OR
>
> second option:
>
>
> Storing objects like : {key :UUID, ConstantString, List<GemFireObject>
> objects} and I can apply both PDX serialization and index(range index)
> on
> field constantString and use == for retrieving objects.
>
> which approach is faster ? first one using LIKe query or second one where
> ==
> is used ?
>
>
>
> --
> Sent from:
> http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
>
