Key indexes tell the query engine that the field is the same as the key that was used to put into the underlying region. So let's say your field is "ID". Creating a key index tells the query engine that a "select * from /region theRegion where ID = 1" is the same as doing : theRegion.get(1).
In this case I think you are looking for a functional index. Those are sorted and will be used for like queries. On Mon, Nov 26, 2018 at 12:52 PM Alexander Murmann <amurm...@pivotal.io> wrote: > Hi, > > Have you thought about using the built-in Lucene functionality for this? > Fuzzy text search is exactly what it's made for. > > On Mon, Nov 26, 2018 at 12:15 PM anjana_nair <siby_sek...@hotmail.com> > wrote: > > > > > Hi, > > > > I would like to add an index to key (keyindex) and the query executed is > > going to be like > > > > "constantstring%" where constant string is going to be the constant > > prefix in a lile query. In this case can we just go ahead with key index > > or > > should we use a function index ? key indexes are not sorted ? > > > > > > > > -- > > Sent from: > > http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/ > > >
