If you are storing the data using pdx auto seriaization the index will work
just fine with your custom object keys.


There is no short answer to how much extra memory overhead an index will
cause because it is dependent on the actual data itself (really the
cardinality of the data). See
https://en.wikipedia.org/wiki/Cardinality_(SQL_statements)

They do tend to be large. Use indices judiciously.



--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771

On Wed, Feb 24, 2016 at 12:34 PM, steve mathew <[email protected]>
wrote:

> Thank you Dan.
>
> Will this work with custom object keys?
> How much will be extra memory overhead when creating index?
>
> Steve.
>
> On Wed, Feb 24, 2016 at 11:36 PM, Dan Smith <[email protected]> wrote:
>
> > Hi Steve,
> >
> > I think your best bet is probably to use an OQL index. You can create an
> > OQL index and then do range queries through OQL.
> >
> > You can see some examples of OQL queries here:
> >
> >
> >
> http://geode.docs.pivotal.io/docs/getting_started/querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E
> >
> > Eg
> > SELECT * from /exampleRegion value WHERE value.ID > startKey AND
> value.ID <
> > endKey
> >
> > -Dan
> >
> > On Tue, Feb 23, 2016 at 10:37 PM, steve mathew <[email protected]
> >
> > wrote:
> >
> > > Hello I am new to the apache geode and exploring a possibility to store
> > > data sorted into regions.
> > >
> > > I need to store data sorted for the scan(startkey, endkey) operation.
> > > Simple looking at the APIs it looks geode is not designed for this. Is
> > > there any way to achieve this?
> > >
> > > Thanks in advance.
> > >
> > > Kindly advise.
> > >
> > > -Steve.
> > >
> >
>

Reply via email to