-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel, thank you very much for the hint!

I stepped through the code and tried some scenarios.

when I type in with whitespace delimiters
~      termA termB
this will result into two invocations of getFieldQuery, one for each term.

when I type
~      termA/termB
or
~     "termA termB"
this will result into one invocation of getFieldQuery for the whole String.

Why makes the parser a difference between termA/termB and termA termB?
The Analyzer tokenizes between both delimiters.


Christian


Daniel Noll schrieb:
| On Tuesday 26 February 2008 01:05:27 [EMAIL PROTECTED] wrote:
|> Hi all,
|>
|> I have the behaviour that when I search with Luke (version 0.7.1, Lucene
|> version 2.2.0) inside an arbritray field, the QueryParser creates a
|> PhraseQuery when I type in
|> ~              termA/termB      (no "...")
|> When I read the documentation at the Lucene webside, I only find the syntax
|> ~             "termA termB"
|> for creating phrase queries.
|>
|> Did I make a mistake? Can I configure the QueryParser that he simply
|> tokenizes between termA and termB, and makes a simple BooleanQuery as he do
|> in the case of a whitespace delimiter?
|
| You'll find they both go through getFieldQuery() as-is.  The default
| implementation of that runs the string through the analyser; if it happens to
| return more than one token then it will create a PhraseQuery instead of a
| TermQuery.
|
| If you subclass QueryParser than you can override this method and modify it to
| do whatever evil trick you want to do.
|
| Daniel
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: [EMAIL PROTECTED]
| For additional commands, e-mail: [EMAIL PROTECTED]
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFHw+HIQoTr50f1tpcRAjPvAKCQCfmQj92RLqIdo4ZdpTmH8repBgCfa+tU
zV0eF04C5ijDXVHkG4J8RiM=
=eupM
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to