No I did not, because I'm not performing a search with a leading
wildcard, nor am I intending to allow that behavior. But what I do want
to be able to search on is a word that starts with a * by escaping it,
because sadly our data contains such things.
Matt
Karl Wettin wrote:
15 maj 2008 kl. 18.33 skrev Matthew Hall:
12:23:05,602 INFO [STDOUT]
org.apache.lucene.queryParser.ParseException: Cannot parse '\*ache*':
'*' not allowed as first character in PrefixQuery
12:23:05,602 INFO [STDOUT] Failure in QS_MarkerSearch.searchMarkerNomen
12:23:05,602 ERROR [STDERR] java.lang.NullPointerException
12:23:05,602 ERROR [STDERR] at
org.jax.mgi.search.model.QS_MarkerSearch.searchInexactMatches(Unknown
Source)
Which looks to me alot like something akin to the
AllowLeadingWildcard stuff that comes along with wildcardqueries.
But, the odd thing is the leading character in my search string ISN'T
*, its the escaped star character, which I would have thought would
work with no problems at all.
Have I stumbled across a bug here?
Did you setAllowLeadingWildcard(true)?
/**
* Set to <code>true</code> to allow leading wildcard characters.
* <p>
* When set, <code>*</code> or <code>?</code> are allowed as
* the first character of a PrefixQuery and WildcardQuery.
* Note that this can produce very slow
* queries on big indexes.
* <p>
* Default: false.
*/
public void setAllowLeadingWildcard(boolean allowLeadingWildcard) {
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Matthew Hall
Software Engineer
Mouse Genome Informatics
[EMAIL PROTECTED]
(207) 288-6012
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
