Re: OAK-4348 - intent to add oak-lucene-mt

I've realised we can actually name it oak-search-mt anyway, as we aim to just implement existing SPIs / plugin; if they are the same or not it doesn't make too much difference for the name itself. I'll see if we can make FulltextQueryTermsProvider somehow work with Solr in the context of OAK-3336

Re: OAK-4348 - intent to add oak-lucene-mt

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

Re: OAK-4348 - intent to add oak-lucene-mt

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 wrote: >

OAK-4348 - intent to add oak-lucene-mt

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