Nested queries might help.
http://www.slideshare.net/erikhatcher/solr-query-parsing-tips-and-tricks
On Mon, Nov 2, 2015 at 10:20 AM, Aaron Gibbons <
agibb...@synergydatasystems.com> wrote:
> The input for the title field is user based so a wide range of things can
> be entered there. Quoting the title is not what I'm looking for. I also
> checked and q.op is AND and MM is 100%. In addition to the Title field the
> user can also use general keywords so setting local params (df) to
> something else would not work either to my knowledge.
>
> To give you a better idea of what I'm trying to accomplish: I have a form
> to allow users to search on Title, Keywords and add a location. The correct
> operators are applied between each of these and also for the main keywords
> themselves. The only issue is with the default operator being applied
> within the Title sections's keywords. My goal is to have the Title keywords
> work the same as the general keywords but only be applied to the title
> field vs the default text field.
>
> On Fri, Oct 30, 2015 at 6:35 PM, davidphilip cherian <
> davidphilipcher...@gmail.com> wrote:
>
> > >> "Is there any way to have a single field search use the same keyword
> > search logic as the default query?"
> > Do a phrase search, with double quotes surrounding the multiple keywords,
> > it should work.
> >
> > Try q=title:("Test Keywords")
> >
> > You could possibly try adding this q.op as local param to query as shown
> > below.
> >
> >
> https://cwiki.apache.org/confluence/display/solr/Local+Parameters+in+Queries
> >
> > If you are using edismax query parser, check for what is mm pram
> > set. q.op=AND => mm=100%; q.op=OR => mm=0%)
> >
> >
> https://wiki.apache.org/solr/ExtendedDisMax#mm_.28Minimum_.27Should.27_Match.29
> >
> >
> > On Fri, Oct 30, 2015 at 3:27 PM, Aaron Gibbons <
> > agibb...@synergydatasystems.com> wrote:
> >
> > > Is there any way to have a single field search use the same keyword
> > search
> > > logic as the default query? I define q.op as AND in my query which gets
> > > applied to any main keywords but any keywords I'm trying to use within
> a
> > > field do not get the same logic applied.
> > > Example:
> > > q=(title:(Test Keywords)) the space is treated as OR regardless of q.op
> > > q=(Test Keywords) the space is defined by q.op which is AND
> > >
> > > Using the correct operators (AND OR * - +...) it works great as I have
> it
> > > defined. There's just this one little caveat when you use spaces
> between
> > > keywords expecting the q.op operator to be applied.
> > > Thanks,
> > > Aaron
> > >
> >
>
