Re: spellchecker problems (bugs)
On Thu, Jul 24, 2008 at 2:59 PM, <[EMAIL PROTECTED]> wrote: > Hi, > > Anyone has probed the patch? I apply it and the problem persists. > I don't know if I am doing something incorrect or the patch has some error. > > Can any one help me? > > Thanks a lot. > > Rober. > This issue has been fixed in the trunk. Can you please use the latest trunk code and try? -- Regards, Shalin Shekhar Mangar.
Re: Seeking Anecdotes: Solr Plugins
I imagined the AnalysisRequestHandler might be useful for serving up vectors for things like machine learning experiments or just as a server that does analysis. Also, someone on dev the other day talked about one that brought back the vectors w/ TF/IDF info as well. I think Solr could make for quite a nice ML server. Also, for Taming Text (again not there yet, but in the works and hopefully done in time for your talk :-) http://manning.com/ ingersoll/), plan to have a Solr server that functions with OpenNLP (http://opennlp.sourceforge.net ) and some other open source tools and can do things like named entity recognition, clustering and classification and make all of those things searchable. Most (if not all) of these things will be done as some type of plugin (ReqHandler, SearchComponent, custom analyzers/ token filters, etc.). Bigger question, though, is why are you preparing for ApacheCon so far in advance? ;-) -Grant On Jul 22, 2008, at 7:34 PM, Chris Hostetter wrote: Hey everybody, I'll be giving a talk called "Apache Solr: Beyond the Box" at ApacheCon this year, which will focus on the how/when/why of writing Solr Plugins... http://us.apachecon.com/c/acus2008/sessions/10 I've got several use cases I can refer to for examples, both from my day job and from public projects (DIH, Local Solr, etc.) but I'm hoping to be able to provide even broader examples of the types of "niche" plugins people have written for specific purposes, and what their motivations where for doing so (as opposed to doing alternate logic in their client). If people would like to reply to this thread to share a little bit of information about their experiences, that would be awesome -- in addition to helping me write my slides, it would help other Solr users be aware of what's possible (and help Solr developers be more aware of how our users are taking advantage of the APIs). If there are reasons why you can't publicly disclose the details of how you are using Solr, but you wouldn't mind sharing some of the info with me directly on the grounds that I keep you (and your company) anonymous you can also feel free to email me directly. -Hoss
Re: spellchecker problems (bugs)
This issue has been fixed in the trunk. Can you please use the latest trunk code and try? current trunk looks good. thanks! --Geoff
Multiple search components in one handler - ie spellchecker
Hello - I am attempting to add the spellCheck component in my "search" requesthandler so when a users does a search, they get the results and spelling corrections all in one query just like the way the facets work. I am having some trouble accomplishing this - can anyone point me to documentation (other than http://wiki.apache.org/solr/SpellCheckComponent) on how to do this or an example solrconfig that would do this correctly? My guess is there is something preventing this from happening since the requesthandler tag is loading the search component and not the spellchecker component? Thanks and sorry if my message is a bit vague Andrew
Re: Multiple search components in one handler - ie spellchecker
Andrew Nagy wrote: Hello - I am attempting to add the spellCheck component in my "search" requesthandler so when a users does a search, they get the results and spelling corrections all in one query just like the way the facets work. I am having some trouble accomplishing this - can anyone point me to documentation (other than http://wiki.apache.org/solr/SpellCheckComponent) on how to do this or an example solrconfig that would do this correctly? http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200806.mbox/[EMAIL PROTECTED] in general, just add the spellcheck bit to your existing handler after following setup in the twiki docs. you can ignore the part about the exceptions, as that has been fixed in trunk. HTH --Geoff
Easiest way to get data dir from a plugin?
How do I get the solr / data dir from a plugin without using anything thats deprecated? - Mark
Re: Easiest way to get data dir from a plugin?
core.getDataDir() what kind of plugin? If you don't have access to core, you can implement SolrCoreAware... On Jul 25, 2008, at 2:27 PM, Mark Miller wrote: How do I get the solr / data dir from a plugin without using anything thats deprecated? - Mark
RE: Multiple search components in one handler - ie spellchecker
Thanks for getting back to me Geoff. Although, that is pretty much what I have. Maybe if I show my solrconfig someone might be able to point out what I have incorrect? The problem is that nothing related to the spelling options are show in the results, just the normal expected search results. Here is my query: http://localhost:8080/solr/select?q=*:*&rows=1&spellcheck=true&spellcheck.q=scandanava&spellcheck.build=true allfields 0.7 ./spellchecker text explicit spellcheck From: Geoffrey Young [EMAIL PROTECTED] Sent: Friday, July 25, 2008 2:13 PM To: solr-user@lucene.apache.org Subject: Re: Multiple search components in one handler - ie spellchecker Andrew Nagy wrote: > Hello - I am attempting to add the spellCheck component in my > "search" requesthandler so when a users does a search, they get the > results and spelling corrections all in one query just like the way > the facets work. > > I am having some trouble accomplishing this - can anyone point me to > documentation (other than > http://wiki.apache.org/solr/SpellCheckComponent) on how to do this or > an example solrconfig that would do this correctly? http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200806.mbox/[EMAIL PROTECTED] in general, just add the spellcheck bit to your existing handler after following setup in the twiki docs. you can ignore the part about the exceptions, as that has been fixed in trunk. HTH --Geoff
Re: Multiple search components in one handler - ie spellchecker
Andrew Nagy wrote: Thanks for getting back to me Geoff. Although, that is pretty much what I have. Maybe if I show my solrconfig someone might be able to point out what I have incorrect? The problem is that nothing related to the spelling options are show in the results, just the normal expected search results. right. the spellcheck component does not issue a separate query *after* running the spellcheck, it merely offers suggestions in parallel with your existing query. the results are more like "below are the results for $query. did you mean $suggestions?" HTH --Geoff
Re: Easiest way to get data dir from a plugin?
Thanks Ryan. Its a SearchComponent. Re: SolrCoreAware: very cool. Had seen it, but didn't follow exactly how it worked. I was grabbing the core off the request, but I really wanted to set the data dir more like in the init rather then having to set it every time, or check and set, during each prepare or process call. SolrCoreAware will solve the issue perfectly I think. Thanks, Mark Ryan McKinley wrote: core.getDataDir() what kind of plugin? If you don't have access to core, you can implement SolrCoreAware... On Jul 25, 2008, at 2:27 PM, Mark Miller wrote: How do I get the solr / data dir from a plugin without using anything thats deprecated? - Mark
RE: Multiple search components in one handler - ie spellchecker
Exactly - however the spellcheck component is not working for my setup. The spelling suggestions never show in the response. I think I have the solrconfig setup incorrectly. Also my solr/data/spell index that is created is empty. Something is not configured correctly, any ideas? Andrew From: Geoffrey Young [EMAIL PROTECTED] Sent: Friday, July 25, 2008 3:04 PM To: solr-user@lucene.apache.org Subject: Re: Multiple search components in one handler - ie spellchecker Andrew Nagy wrote: > Thanks for getting back to me Geoff. Although, that is pretty much > what I have. Maybe if I show my solrconfig someone might be able to > point out what I have incorrect? The problem is that nothing related > to the spelling options are show in the results, just the normal > expected search results. right. the spellcheck component does not issue a separate query *after* running the spellcheck, it merely offers suggestions in parallel with your existing query. the results are more like "below are the results for $query. did you mean $suggestions?" HTH --Geoff
Re: Multiple search components in one handler - ie spellchecker
On Sat, Jul 26, 2008 at 12:37 AM, Andrew Nagy <[EMAIL PROTECTED]> wrote: > Exactly - however the spellcheck component is not working for my setup. > The spelling suggestions never show in the response. I think I have the > solrconfig setup incorrectly. Also my solr/data/spell index that is created > is empty. Something is not configured correctly, any ideas? > > Andrew > > From: Geoffrey Young [EMAIL PROTECTED] > Sent: Friday, July 25, 2008 3:04 PM > To: solr-user@lucene.apache.org > Subject: Re: Multiple search components in one handler - ie spellchecker > > Andrew Nagy wrote: > > Thanks for getting back to me Geoff. Although, that is pretty much > > what I have. Maybe if I show my solrconfig someone might be able to > > point out what I have incorrect? The problem is that nothing related > > to the spelling options are show in the results, just the normal > > expected search results. > > right. the spellcheck component does not issue a separate query *after* > running the spellcheck, it merely offers suggestions in parallel with > your existing query. > > the results are more like > > "below are the results for $query. did you mean $suggestions?" > > HTH > > --Geoff > > > Is the allfields in your spell checker configuration in your schema.xml? Can you see the spellcheckIndexDir created inside the Solr's data directory? -- Regards, Shalin Shekhar Mangar.
Re: solr synonyms behaviour
swarag wrote: > > > Yonik Seeley wrote: >> >> On Tue, Jul 15, 2008 at 2:27 PM, swarag <[EMAIL PROTECTED]> >> wrote: >>> To my understanding, this means I am using synonyms at index time and >>> NOT >>> query time. And yet, I am still having these problems with synonyms. >> >> Can you give a specific example? Use debugQuery=true to see what the >> resulting query is. >> You can also use the admin analysis page to see what the output of the >> index and query analyzers. >> >> -Yonik >> >> > > So it sounds like using the '=>' operator for synonyms that may or may not > contain multiple words causes problems. So I changed my synonyms.txt to > the following: > > club,bar,night cabaret > > In schema.xml, I now have the following: > positionIncrementGap="100"> > > > ignoreCase="true" expand="true"/> > words="stopwords.txt" enablePositionIncrements="true"/> > generateWordParts="1" generateNumberParts="1" catenateWords="1" > catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/> > > protected="protwords.txt"/> > > > > > words="stopwords.txt"/> > generateWordParts="1" generateNumberParts="1" catenateWords="0" > catenateNumbers="0" catenateAll="0" splitOnCaseChange="1"/> > > protected="protwords.txt"/> > > > > > As you can see, 'night cabaret' is my only multi-word synonym term. > Searches for 'bar' and 'club' now behave as expected. However, if I > search for JUST 'night' or JUST 'cabaret', it looks like it is still using > the synonyms 'bar' and 'club', which is not what is desired. I only want > 'bar' and 'club' to be returned if a search for the complete 'night > cabaret' is submitted. > > Since query-time synonyms is turned "off", the resulting > parsedquery_toString is simply "name:night", "name:cabaret", etc... > > Thanks! > We are still having problems. Searches for single words that are part of a multi-word synonym seem to be affected by the synonyms, when they should not. Anyone else experience this? If not, would you mind explaining your config and the format of your synonyms.txt file? -- View this message in context: http://www.nabble.com/solr-synonyms-behaviour-tp15051211p18660135.html Sent from the Solr - User mailing list archive at Nabble.com.
