You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by bu...@apache.org on 2003/09/22 01:00:07 UTC

DO NOT REPLY [Bug 23308] - [1.3RC1] QueryParser should handle Query.toString()

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=23308>.
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=23308

[1.3RC1] QueryParser should handle Query.toString()





------- Additional Comments From jakarta@ehatchersolutions.com  2003-09-21 23:00 -------
There should not be any dependency on QueryParser by Query classes.  QueryParser in Lucene's 
codebase is a convenience "factory" for a Query, but should not be coupled in the direction you 
propose.

How about creating a custom TermQuery subclass that has your custom toString method in it, and 
then use that in your custom QueryParser instead of the builtin TermQuery?