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%20israel&spellcheck.q=american%20israel&qt=spellchecker
(with
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 "" *into* the requestHandler,
but of course it does not work.
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 wrote:
> Thanks, but i have
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:
http://lucene.472066.n3.nabble.com/Full-sentence-s
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 b
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;
/**
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 A
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
My analyser is not empty :
/
/
and i'm sure there is words in it
I don't know where to find this file
"org.apache.solr.handler.component.SpellCheckComponent.getTokens"
--
View this message in context:
http://lucene.472066.n3.nabble.com/Full-se
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 wrote:
> Line 476 of SpellCheckComponent.getTokens of mine is assert analyzer !=
> null;
> it seems our codes' versions don't match. could you decompile your
> SpellCheckComponent
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 wrote:
> My beautiful NullPointer Exception :
>
>
> SEVERE: java.lang.NullPoin
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
o
NullPointerException? do you have the full exception print stack?
On Fri, Aug 19, 2011 at 6:49 PM, Valentin 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 what I do with my
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 pos
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
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:
http://lucene.472066.n3.nabble.com/Full-sentence-spellcheck-tp3265257p3267629.
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 wrote:
> I'm trying to configure a spellchecker to autocomplete full sentences from my
> query.
>
> I've
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.
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 [mailto:igorlac
19 matches
Mail list logo
