: I'll catch that and deal with it then (Or is it bad programming ?) .
that's a psuedo-religious question -- i will only say that many people
recomend against using Exception catching to drive control flow, it's
called an "Exception" because it's suppose to be the "Exception" to the
norm ... i
On Tue, Oct 7, 2008 at 12:56 AM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
>
> : req.getSchema().getQueryAnalyzer();
> :
> : I think it's in this analyzer that the undefined field error happens
> : (because for instance the field 'foo' doesn't exists in the schema,
> : and so it's impossible to fi
: req.getSchema().getQueryAnalyzer();
:
: I think it's in this analyzer that the undefined field error happens
: (because for instance the field 'foo' doesn't exists in the schema,
: and so it's impossible to find a specific analyzer to this field in
: the schema).
Correct.
: The strange thing
Hi,
yes I've got the stack trace giving me the beginning of an explanation.
One of the QueryParsers I use in my Query parser plugin is a
multifiedQueryParser and it needs a fields aware Analyzer, which I get
from the schema like this:
req.getSchema().getQueryAnalyzer();
I think it's in this
On Tue, Sep 30, 2008 at 2:42 PM, Jérôme Etévé <[EMAIL PROTECTED]> wrote:
> But still I have an error from the webapp when I try to query my
> schema with non existing fields in my query ( like foo:bar ).
>
> I'm wondering if the query q is parsed in a very simple way somewhere
> else (and independe
