I second this notion. My reasoning focuses mostly on maintainability, where I posit that your client code will be far easier to extend/modify/troubleshoot than any effort spent attempting to do this within Solr.
Jason On Dec 23, 2013, at 12:07 PM, Joel Bernstein <joels...@gmail.com> wrote: > I would suggest handling this in the client. You could write custom Solr > code also but it would be more complicated because you'd be working with > Solr's API's. > > Joel Bernstein > Search Engineer at Heliosearch > > > On Mon, Dec 23, 2013 at 2:36 PM, jmlucjav <jmluc...@gmail.com> wrote: > >> Hi, >> >> I have this scenario that I think is no unusual: solr will get a user >> entered query string like 'apple pear france'. >> >> I need to do this: if any of the terms is a country, then change the query >> params to move that term to a fq, i.e: >> q=apple pear france >> to >> q=apple pear&fq=country:france >> >> What do you guys would be the best way to implement this? >> - custom searchcomponent or queryparser >> - servlet in same jetty as solr >> - client code >> >> To simplify, consider countries are just a single term. >> >> Any pointer to an example to base this on would be great. thanks >>
