Re: Full sentence spellcheck

2011-08-24 Thread Valentin
I've run some tests, and I found that it makes this error when i add a spellcheck component to a handler and i try to use spellcheck.q So spellcheck.q works with this kind of use : http://localhost:8983/solr/db/suggest_full?q=american%20israelspellcheck.q=american%20israelqt=spellchecker (with

Re: Full sentence spellcheck

2011-08-23 Thread Valentin
I tried your solution, it works. But it modify all the spellcheckers that I made, so that's not a good solution for me (I have an autocomplete and a regular spellcheck with separated words that I want to keep). I tried to move the line queryConverter name=queryConverter

Re: Full sentence spellcheck

2011-08-22 Thread Valentin
I found the thread Suggester Issues. You said to write a new java class : package com.civicscience; import java.util.ArrayList; import java.util.Collection; import java.util.Collections; import org.apache.lucene.analysis.Token; import org.apache.solr.spelling.QueryConverter; /**

Re: Full sentence spellcheck

2011-08-22 Thread William Oberman
I listed the basic steps I took in the other thread (recently), which were: -Downloaded apache-solr-3.3.0 archive (I like to stick with releases vs. svn) -Untar (tar -xzvf) and cd -ant (to compile) -mkdir something, cd something (e.g. create a peer directory in apache-solr-3.3.0) -Wrote my class

Re: Full sentence spellcheck

2011-08-22 Thread Valentin
Thanks, but i have a last question before trying your solution : did you have the same NullPointerException before ? I want to be sure that is the only way to resolve my problem before midifying some java files... -- View this message in context:

Re: Full sentence spellcheck

2011-08-22 Thread William Oberman
I had an NPE on the same line, but from googling it seems like that NPE can happen for different reasons, so I couldn't say if my situation was exactly the same as yours. I will say I get phrase based suggestions now. will On Mon, Aug 22, 2011 at 11:28 AM, Valentin igorlacro...@gmail.com wrote:

RE: Full sentence spellcheck

2011-08-19 Thread Valentin
Actually, that's not my problem, I do specify q. Another idea ? It really makes me crazy... -- View this message in context: http://lucene.472066.n3.nabble.com/Full-sentence-spellcheck-tp3265257p3267394.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Full sentence spellcheck

2011-08-19 Thread Li Li
this may need something like language models to suggest. I found an issue https://issues.apache.org/jira/browse/SOLR-2585 what's going on with it? On Thu, Aug 18, 2011 at 11:31 PM, Valentin igorlacro...@gmail.com wrote: I'm trying to configure a spellchecker to autocomplete full sentences

Re: Full sentence spellcheck

2011-08-19 Thread Valentin
I don't think it wil lhelp me, sorry. I just want my query to not be tokenised, I want it to be considered as a full sentence to correct. But thanks for your answers, I keep searching. -- View this message in context:

Re: Full sentence spellcheck

2011-08-19 Thread Li Li
I haven't used suggest yet. But in spell check if you don't provide spellcheck.q, it will analyze the q parameter by a converter which tokenize your query. else it will use the analyzer of the field to process parameter q. If you don't want to tokenize query, you should pass spellcheck.q

Re: Full sentence spellcheck

2011-08-19 Thread Valentin
Li Li wrote: If you don't want to tokenize query, you should pass spellcheck.q and provide your own analyzer such as keyword analyzer. That's already what I do with my suggestTextFull fieldType, added to my searchComponent, no ? I've copied my fieldType and my searchComponent on my first

Re: Full sentence spellcheck

2011-08-19 Thread Li Li
NullPointerException? do you have the full exception print stack? On Fri, Aug 19, 2011 at 6:49 PM, Valentin igorlacro...@gmail.com wrote: Li Li wrote: If you don't want to tokenize  query, you should pass spellcheck.q and provide your own analyzer such as keyword analyzer. That's already

Re: Full sentence spellcheck

2011-08-19 Thread Valentin
My beautiful NullPointer Exception : SEVERE: java.lang.NullPointerException at org.apache.solr.handler.component.SpellCheckComponent.getTokens(SpellCheckComponent.java:476) at org.apache.solr.handler.component.SpellCheckComponent.process(SpellCheckComponent.java:131) at

Re: Full sentence spellcheck

2011-08-19 Thread Li Li
Line 476 of SpellCheckComponent.getTokens of mine is assert analyzer != null; it seems our codes' versions don't match. could you decompile your SpellCheckComponent.class ? On Fri, Aug 19, 2011 at 7:23 PM, Valentin igorlacro...@gmail.com wrote: My beautiful NullPointer Exception : SEVERE:

Re: Full sentence spellcheck

2011-08-19 Thread Li Li
or your analyzer is null? any other exception or warning in your log file? On Fri, Aug 19, 2011 at 7:37 PM, Li Li fancye...@gmail.com wrote: Line 476 of  SpellCheckComponent.getTokens of mine  is  assert analyzer != null; it seems our codes' versions don't match. could you decompile your

Re: Full sentence spellcheck

2011-08-19 Thread Valentin
My analyser is not empty : /fieldType name=suggestTextFull class=solr.TextField analyzer type=index tokenizer class=solr.KeywordTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.RemoveDuplicatesTokenFilterFactory/ /analyzer analyzer type=query

Re: Full sentence spellcheck

2011-08-19 Thread Will Oberman
This might be unrelated, but I had the exact same error yesterday trying to replace the query converter with a custom class I wrote. Ended up, I wasn't properly registering my jar. I'm still testing with jetty, and lib in example is included too late in the startup process. I had to

Re: Full sentence spellcheck

2011-08-19 Thread William Oberman
I was on my phone before, and didn't see the whole thread. I wanted the same thing, to have spellchecker not tokenize. See the Suggester Issues thread for my junky replacement class that doesn't tokenize (as far as I can tell from a few minutes of testing). will On Aug 19, 2011, at 8:35

RE: Full sentence spellcheck

2011-08-18 Thread Dyer, James
If you use spellcheck.q, you also still need to specify q for the queryhandler, otherwise you'll get an NPE. Not sure that's your problem but its one thing to check. James Dyer E-Commerce Systems Ingram Content Group (615) 213-4311 -Original Message- From: Valentin