|
|
 |
|
 |
|
On Wed, 1 Feb 2012 15:02:12 -0800 (PST), Chris Hostetter <...@fucit.org
: So it seems like it just broke the text up at spaces, and does text analysis
: within getFieldQuery(), but how can it make the assumption that text should
: only be broken at whitespace ?
whitespace is a significant metacharacter to the Queryparser - it is used
to distinguish multiple clauses of a BooleanQuery.
if you want whitepace to be treated as a literal part of the query, you
need to either escape it, or quote it...
dug\ up
"dug up"
: This seemed to be confirmed that when i pass it query 'dug/up' it just passes
: it as one string, but then its seems to get converted to 'dug up' within the
: getFieldQuery()
getFieldQuery is responsible for calling the analyzer - so in your
'dug/up' example the analyzer you are using in your QueryParser instance
is evidently tokenizing on "/"
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: java...@lucene.apache.org
For additional commands, e-mail: java...@lucene.apache.org
|
|
 |
|
 |
|
|
|
|
On Wed, 1 Feb 2012 17:03:21 -0500, Robert Muir <...@gmail.com
On Wed, Feb 1, 2012 at 4:32 PM, Paul Taylor <...@fastmail.fm
you are right, see this bug report:
https://issues.apache.org/jira/browse/LUCENE-2605
--
lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java...@lucene.apache.org
For additional commands, e-mail: java...@lucene.apache.org
|
|
|
|
|
|
|
|
|
On Wed, 01 Feb 2012 23:45:43 +0000, Paul Taylor <...@fastmail.fm
I've voted on it, although reading the Hoss Mans reply I understand the
issue.
In my particular case I add album catalogsno to my index as a keyword
field , but of course if the cat log number contains a space as they
often do (i.e. cad 6) there is a mismatch. Ive now changed my indexing
to index the value as 'cad6' removing spaces. Now if the query sent to
the query parser is just
cad 6
there is the issue that it breaks them up into two separate fields ,
but I thought it that if the query sent to the parser was
"cad 6"
then the complete string would be passed using the analyzer , but it
doesn't seem to quite work, it creates a TermQuery instead of a
PhraseQuery , yet the explain shows the query to have the value
catno:cad 6
rather than
catno:cad6
and I dont get a match, what does that mean ?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java...@lucene.apache.org
For additional commands, e-mail: java...@lucene.apache.org
|
|
|
|
|
|
|
|
|
On Thu, 2 Feb 2012 09:27:04 +0200, Doron Cohen <...@gmail.com
Seems like at query time a KeywordAnalyzer was applied, while at indexing
time additional logic of removing spaces was (first) applied, therefore the
different results at indexing and search.
Doron
|
|
|
|
|
|
|
|
|
On Thu, 02 Feb 2012 08:26:17 +0000, Paul Taylor <...@fastmail.fm
Hi, sort of I had an error in the reusableTokenStream() method of my
analyzer, so it wasn't doing the full analysis at query time, working now.
thanks Paul
|
|
|
|
|
|
|