Is this a replacement for IndexingSpi? Put bluntly, do we deprecate (and remove) it?
Or do you see them as complimentary? > On 12 Apr 2021, at 11:29, Maksim Timonin <timonin.ma...@gmail.com> wrote: > > Hi Stephen! > > Please have a look at the QueryProcessing paragraph [1]. I've described > why IndexingSpi doesn't fit us well. > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-71+Public+API+for+secondary+index+search#IEP71PublicAPIforsecondaryindexsearch-2)QueryProcessing > > On Mon, Apr 12, 2021 at 1:24 PM Stephen Darlington < > stephen.darling...@gridgain.com> wrote: > >> How does this fit with the current IndexingSpi? Superficially they appear >> to do very similar things? >> >> Regards, >> Stephen >> >>> On 6 Apr 2021, at 14:13, Maksim Timonin <timonin.ma...@gmail.com> wrote: >>> >>> Hi, Igniters! >>> >>> I'd like to propose a new feature - opportunity to query and create >> indexes >>> from public API. >>> >>> It will help in some cases, where: >>> 1. SQL is not applicable by design of user application; >>> 2. Where IndexScan is preferable than ScanQuery for performance reasons; >>> 3. Functional indexes are required. >>> >>> Also it'll be great to have a transactional support for such queries, >> like >>> the "select for update" query provides. But I don't dig there much. It >> will >>> be a next step if this API will be implemented. >>> >>> I've prepared an IEP-71 for that [1] with more details. Please share your >>> thoughts. >>> >>> >>> [1] >>> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-71+Public+API+for+secondary+index+search >> >> >>
