"
> >>
> >> You can create an index on the map to optimize this sort of query
> >>
> >> gfsh>create index --name="IndexName" --expression="r.column2[*]"
> >> --region="/exampleRegion r"
>
e.apache.org/docs/guide/112/developing/query_index/creating_map_indexes.html
>>
>> In addition, I noticed that your value implements Serializable. You will
>> get better performance out of the query engine if you configure PDX
>> serialization for your object, either by conf
ps://geode.apache.org/docs/guide/112/developing/query_index/creating_map_indexes.html
>>
>> In addition, I noticed that your value implements Serializable. You will
>> get better performance out of the query engine if you configure PDX
>> serialization for your object, eith
rmance out of the query engine if you configure PDX
> serialization for your object, either by configuring the auto serializer or
> implementing PdxSerializable. That avoids the need to deserialize your
> entire value on the server to query/index it.
>
> -Dan
>
>
> _
need to deserialize your entire value on the
server to query/index it.
-Dan
From: ankit Soni
Sent: Friday, January 29, 2021 9:32 AM
To: dev@geode.apache.org
Subject: Inputs for efficient querying
Hello Team,
I am loading data into Geode (V 1.12) with the following *Key (o
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
