How to suggest prefix matches over all tokens of a field (was Re: Suggest Component, prefix match (sur-)name)

2019-02-18 Thread David '-1' Schmid
On 2019-02-18T18:12:44, David '-1' Schmid wrote: > Will report back if that's working out. It's working! If anybody want's to replicate, here's what I ended up with. .. managed-schema: . . . . . . . . . . . . . . . . . . . . . . . . . .

Re: Suggest Component, prefix match (sur-)name

2019-02-18 Thread David '-1' Schmid
Hello again! After playing around with more simple solutions, I gather the suggester cannot do this. I've found a resource (namely 'Solr in Action'), they use a combination of - two copyFields: - solr.TextField with simple whitespace tokenizer (field:'words') - as above, but with added EdgeNG

Re: Suggest Component, prefix match (sur-)name

2019-02-17 Thread David '-1' Schmid
Hi Lev, On 2019-02-15T17:14:50, Tannen, Lev (USAEO) [Contractor] wrote: > If I understood your requirement correctly you should use "AND" rather > than "or". Also I, believe, "AND" should be in capital letters, but I > am not sure. I think that the suggestion query does not support boolean logic

RE: Suggest Component, prefix match (sur-)name

2019-02-15 Thread Tannen, Lev (USAEO) [Contractor]
Hi David, If I understood your requirement correctly you should use "AND" rather than "or". Also I, believe, "AND" should be in capital letters, but I am not sure. Good luck. Lev Tannen -Original Message- From: David '-1' Schmid Sent: Friday, February 15, 2019 10:23 AM To: solr-user@

Re: Suggest component

2011-12-13 Thread kmf
I think I may have solved my problem. Not 100% certain what the solution was because I've been trying so many things, but in the end what I did was revisit this article and re-step my configuration. http://www.lucidimagination.com/blog/2011/04/08/solr-powered-isfdb-part-9/ I believe what the pro

Re: Suggest component

2011-12-09 Thread kmf
Thanks for the reply. Yes, all are indexed=true (name_auto and the copyField items). Here are the snippets from schema.xml (didn't want to post the whole thing because the following is what I've changed/added)

Re: Suggest component

2011-12-09 Thread Erick Erickson
Is the field indexed? I.e. indexed="true"? Just because you see values there when you specify it in fl only says it's stored, not whether it's available from the in ed terms. You might show us your schema file... Best Erick On Dec 9, 2011 2:33 PM, "kmf" wrote: > I have the same exact problem as t

Re: Suggest component

2011-12-09 Thread kmf
I have the same exact problem as the OP and can't seem to figure out why it's not working. The indexed field to derive suggestions from is "name_auto" which is of type "text_general" in schema.xml. I made some copyFields to have certain fields be put into "name_auto." I can see that "name_auto"

Re: Suggest component

2011-03-28 Thread Grijesh
have you checked with q=*:*? You mentioned in config buildOnCommit=true So have you checked that your indexing process ends with commit? - Thanx: Grijesh www.gettinhahead.co.in -- View this message in context: http://lucene.472066.n3.nabble.com/Suggest-component-tp2725438p2747100.html Sent