+1
To be clear we are removing "search()" and replacing this with methods that
reflect the return types...
E.g: findKeys() - Returns only the region keys for matched query.
This provides applications flexibility of working with only keys or to
fetch region values as required.
-Anil.
On Mon, Jun 20, 2016 at 10:36 AM, Dan Smith <dsm...@pivotal.io> wrote:
> Hi team,
>
> The lucene integration work is still ongoing. We'd like to make a few
> changes to the API that was proposed on the wiki. The proposal is to add a
> few more methods to the LuceneQuery class to return different types of
> results:
>
> LuceneQuery<K,V> {
> Collection<K> findKeys();
> Collection<V> findValues();
> Collection<LuceneResultStruct<K,V>> findResults();
>
> //This is just the search method and LuceneQueryResults renamed
> //to indicate these classes are specific to getting pages of results
> PageableLuceneQueryResults findPages()
> }
>
> In addition, since the projection fields are not yet implemented, we'd like
> to remove LuceneQueryFactory.setProjectionFields and
> LuceneResultStruct.getProjectionField from the code. They can be added in
> when they are actually implemented.
>
> https://cwiki.apache.org/confluence/display/GEODE/Text+Search+With+Lucene
>
> -Dan
>
