On Thu, Jun 9, 2016 at 11:06 AM, Doug Turnbull < dturnb...@opensourceconnections.com> wrote:
> Honestly half the time I run into this problem, I end up creating a > QParserPlugin because I need to do something specific. With a QParserPlugin > I can run whatever analysis, slicing and dicing of the query string to > manually construct whatever I need to > > > http://www.supermind.org/blog/1134/custom-solr-queryparsers-for-fun-and-profit > > One thing I often do is repeat the functionality of Elasticsearch's match > query. Elasticsearch's match query does the following: > Thanks Doug... I was surprised at the lack of response on this as it seems like it would be a lot more common issue. Looking over that page though, I am not sure I would be able to figure out how to do that kind of custom query parser on my own, without something fairly similar in respect to adding synonym support to work from. I'm just a lowly self-taught web developer after all, not a java programmer or someone with a lot of experience writing source code, etc. We did consider switching to ElasticSearch due to its support out of the box for multi-term synonyms, but that would be a lot of work, and I'm not sure it can support everything else we are doing, like all the nested facets and grouping, etc. and it would take a fair amount of work to convert everything we have to the point of finding that out. I'm wondering if anyone has experience using the autophrasing solution on the Lucidworks blog: https://lucidworks.com/blog/2014/07/12/solution-for-multi-term-synonyms-in-lucenesolr-using-the-auto-phrasing-tokenfilter/ I know I tried this one as well some months ago and couldn't seem to get it to work but it's probably the one I'll be trying next and hopefully can figure it out this time. Since it works as a filter, it should work better for us in terms of being able to apply it selectively only to certain fields. Sent with MailTrack <https://mailtrack.io/install?source=signature&lang=en&referral=mjsmin...@gmail.com&idSignature=22>
