yes, of course it can work the same way with the Solr index, provided we can generalize the FulltextQueryTermsProvider API in a way that avoids any additional network roundtrips (so it needs to be done before "sending" the query to Solr).
In terms of backward compatibility we will need to see how to possibly keep the same package for FulltextQueryTermsProvider and make it available to Solr. Thanks, Tommaso Il giorno ven 25 ago 2017 alle ore 09:50 Chetan Mehrotra < [email protected]> ha scritto: > This looks interesting!. > > Is this bound to Lucene or can possibly be used for Solr also (if we > generalize FulltextQueryTermsProvider concept). If yes then we can > name the module as oak-search-mt > Chetan Mehrotra > > > On Fri, Aug 25, 2017 at 1:14 PM, Tommaso Teofili > <[email protected]> wrote: > > Hi all, > > > > as part of OAK-4348 [1] some time ago I had developed an extension in > > oak-lucene to expand search terms using machine translated term, in order > > to provide cross language search capabilities to Oak (via > > FulltextQueryTermsProvider API [2]). > > In the context of a better modularized Oak, I was thinking to provide > such > > an extension as a separate module (e.g. called oak-lucene-mt), which > would > > be optional. > > In order to use it a language pack would need to be downloaded, for > example > > from [3]. > > Please let me know if there's any concern or feedback. > > > > Regards, > > Tommaso > > > > [1] : https://issues.apache.org/jira/browse/OAK-4348 > > [2] : > > > https://github.com/apache/jackrabbit-oak/blob/trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/spi/FulltextQueryTermsProvider.java > > [3] : https://cwiki.apache.org/confluence/display/JOSHUA/Language+Packs >
