well, to sum it up... it doesn't really matter if I use standard or
dismax, at the moment both give me NullPointers for the same query,
although I didn't change anything since it was working ... it seems
totally random, sometimes it works a couple of times, sometimes it
doesn't :(
Weird...
Hi all,
wow, this is weird...
now before I file the JIRA issue - one thing I forgot to mention is that
I am using the edismax query parser.
I've just done the following:
1) searched with edismax parser:
/select?indent=on&version=2.2&q=beffy&fq=&start=0&rows=10&fl=*%2Cscore&qt=dismax&wt=standa
Sure, no problem, I'll submit a JIRA entry :)
Am 21.09.2010 16:13, schrieb Robert Muir:
I don't think you should get an error like this from SynonymFilter... would
you mind opening a JIRA issue?
On Tue, Sep 21, 2010 at 9:49 AM, Stefan Moises wrote:
Hi again,
well it turns out that it sti
I don't think you should get an error like this from SynonymFilter... would
you mind opening a JIRA issue?
On Tue, Sep 21, 2010 at 9:49 AM, Stefan Moises wrote:
> Hi again,
>
> well it turns out that it still doesn't work ...
> Sometimes it works (i.e. for some cores), sometimes I still get the
Hi again,
well it turns out that it still doesn't work ...
Sometimes it works (i.e. for some cores), sometimes I still get the
nullpointer - e.g. if I create a new core and use the same settings as a
working one, but index different data, then I add a synonym (e.g. "foo
=> bar") and activate
doh, looks like I only forgot to add the spellcheck component to my
edismax request handler... now it works with:
...
spellcheck
elevator
What's strange is that spellchecking seemed to work *without* that
entry, too
Cheers,
Stefan
Am 01.09.2010 13:33, schrieb Stefan Moises:
Hi ther
