Mailing List Archive: DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more)

DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more)

bugzilla at apache

Apr 3, 2002, 1:28 AM

Post #1 of 6 (748 views)

Permalink

DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more) [ In reply to ]

bugzilla at apache

Apr 3, 2002, 9:12 AM

Post #2 of 6 (738 views)

Permalink

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7710>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7710

Wildcard query only accepts 1 or more characters for prefixes (not 0 or more)

otis@apache.org changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED

------- Additional Comments From otis@apache.org 2002-04-03 16:12 -------
Hm, I can't duplicate the behaviour you describe.
I have an index with a few travel-related entries.
When I search for travel I get 1 match containing "Land a hot travel deal ...."
When I search for travel* I get 2 matches. The first one is the same as the one
above, and the second one contains "Travelocity.com" in the indexed field.

Doesn't the fact that a search for travel* matches entries that contain only the
term "travel", and no other terms with "travel" as their base, confirm that
wildcards work properly, matching zero or more characers, even when used at the
end of the query string?

--
To unsubscribe, e-mail: <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>

DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more) [ In reply to ]

bugzilla at apache

Apr 4, 2002, 12:51 AM

Post #3 of 6 (739 views)

Permalink

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7710>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7710

Wildcard query only accepts 1 or more characters for prefixes (not 0 or more)

------- Additional Comments From lee@grantadesign.com 2002-04-04 07:51 -------
Is that definitely using the WildcardQuery class? I know the query parser
defaults to using PrefixQuery for wildcards at the end of the term. In
PrefixQuery, the bug does not seem to be present. However, I'm able to search
for words in my indexes, get results, then search again using WildcardQuery with
a * character at the end, and get zero results.

--
To unsubscribe, e-mail: <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>

DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more) [ In reply to ]

bugzilla at apache

Apr 4, 2002, 9:11 AM

Post #4 of 6 (745 views)

Permalink

DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more) [ In reply to ]

bugzilla at apache

Apr 5, 2002, 2:05 AM

Post #5 of 6 (739 views)

Permalink

DO NOT REPLY [Bug 7710] - Wildcard query only accepts 1 or more characters for prefixes (not 0 or more) [ In reply to ]

bugzilla at apache

Apr 9, 2002, 9:07 PM

Post #6 of 6 (752 views)

Permalink