Re: Selective field query

The first thing I would suggest you is the use of the Analysis tool, to explore your analysis at query and index time. This will be the first step to understand if you are actually tokenising and token filtering as expected. Then you should play with different fields ( in the case the original

Re: Selective field query

Thanks Scot. That is definitely moving things in the right direction I have another question that relates to this. It is also requested to implement a partial word search on the service name field. However, each service also has a unique identifier (string). This field requires exact string

Re: Selective field query

Thanks Alessandro, Certainly the use of the Analysis tool, along with debug query supplies a lot of useful information. I've found that a combination of using the ngram field, (as detailed previously), along with the qf param of the edismax parser seems to be working well. >From there I can

Re: Selective field query

Thanks Erick, I'm sure this will be valuable in implementing ngram filter factory On Fri, Oct 9, 2015 at 4:38 PM, Erick Erickson wrote: > Colin: > > Adding =all to your query is your friend here, the > parsed_query.toString will show you exactly what > is searched

Re: Selective field query

Colin, The other thing you'll want to keep in mind (and you'll find this out with debugQuery) is that the query parser is going to take your ServiceName:(Search Service) and turn it into two queries -- ServiceName:(Search) ServiceName:(Service). That's because the query parser breaks on

Selective field query

Hi I am working on a complex search utility with an index created via data import from an extensive MySQL database. There are many ways in which the index is searched. One of the utility input fields searches only on a Service Name. However, if I target the query as q=ServiceName:"Searched

Re: Selective field query

On Fri, Oct 9, 2015, at 09:54 AM, Colin Hunter wrote: > Hi > > I am working on a complex search utility with an index created via data > import from an extensive MySQL database. > There are many ways in which the index is searched. One of the utility > input fields searches only on a Service

Re: Selective field query

Ah ha... the copy field... makes sense. Thank You. On Fri, Oct 9, 2015 at 10:04 AM, Upayavira wrote: > > > On Fri, Oct 9, 2015, at 09:54 AM, Colin Hunter wrote: > > Hi > > > > I am working on a complex search utility with an index created via data > > import from an

Re: Selective field query

Colin: Adding =all to your query is your friend here, the parsed_query.toString will show you exactly what is searched against. Best, Erick On Fri, Oct 9, 2015 at 2:09 AM, Colin Hunter wrote: > Ah ha... the copy field... makes sense. > Thank You. > > On Fri, Oct 9,