Re: pf doesn't work like normal phrase query

2015-01-11 Thread Michael Lackhoff
Thanks everyone for all the advice! To sum up there seems to be no easy solution. I only have the option to either - make things really complicated - only help some users/query structures - accept the status quo What could help is an analogon to field aliases: If it was possible to say f.title.pf

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Ahmet Arslan
Hi Michael, I had to deal such expert users in the past :) I suggest you to create a new syntax for exact match. Since he is an expert he will love it. either suggest i) ask user to enter number of tokens e.g. q=title:Anatomie AND length:1 or ii) use dollar sign (or something else) for art

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Jack Krupansky
Thanks for the clarification. The issue still remains that you need to distill all of the competing requirements into a single, concise, and consistent model, and whether that adequately aligns with existing Solr features remains problematic. The general guidance is to stick with the existing Solr

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Alexandre Rafalovitch
For the title searches, Doug Turnbull wrote a really interesting in-depth article: http://opensourceconnections.com/blog/solr/using-solr-cloud-for-robustness-but-returning-json-format/ I don't know if that's the one you read already. For the fielded query, you get more flexibility if you use multi

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Michael Lackhoff
Am 11.01.2015 um 18:30 schrieb Jack Krupansky: > It's still not quite clear to me what your specific goal is. From your > vague description it seems somewhat different from the blog post that you > originally cited. So, let's try one more time... explain in plain English > what use case you are tr

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Jack Krupansky
It's still not quite clear to me what your specific goal is. From your vague description it seems somewhat different from the blog post that you originally cited. So, let's try one more time... explain in plain English what use case you are trying to satisfy. You mention fielded queries, but in my

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Michael Lackhoff
Hi Ahmet, > You might find this useful : > https://lucidworks.com/blog/whats-a-dismax/ I have a basic understanding but will do further reading... > Regarding your example : title:foo AND author:miller AND year:[2010 TO *] > last two clauses better served as a filter query. > > http://wiki.apa

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Ahmet Arslan
Hi, You might find this useful : https://lucidworks.com/blog/whats-a-dismax/ Regarding your example : title:foo AND author:miller AND year:[2010 TO *] last two clauses better served as a filter query. http://wiki.apache.org/solr/CommonQueryParameters#fq By the way it is possible to combine di

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Michael Lackhoff
Am 11.01.2015 um 14:19 schrieb Michael Lackhoff: > Or put another way: How can I do this boost in more complex queries like: > title:foo AND author:miller AND year:[2010 TO *] > It would be nice to have a title "foo" before another title "some foo > and bar" (given the other criteria also match bo

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Michael Lackhoff
Am 11.01.2015 um 14:01 schrieb Ahmet Arslan: > What happens when you do not use fielded query? > > q=anatomie&qf=title_exact > instead of > > q=title_exact:"anatomie" Then it works (with qf=title): +(title:anatomie) (title_exact:" anatomie "^20.0) Only problem is that my frontend alway

Re: pf doesn't work like normal phrase query

2015-01-11 Thread Ahmet Arslan
What happens when you do not use fielded query? q=anatomie&qf=title_exact instead of q=title_exact:"anatomie" Ahmet On Sunday, January 11, 2015 12:05 PM, Michael Lackhoff wrote: My aim is to boost "exactish" matches similar to the recipe described in [1]. The anchoring works in q but not in