[ http://issues.apache.org/jira/browse/LUCENE-489?page=comments#action_12443937 ] Steven Parkes commented on LUCENE-489: --------------------------------------
Ah. I get it. Yeah, it is ready to be committed (at least I think it is). In terms of the "patch available" flag (which I appreciate you watching), I figure that's the flag that the assignee thinks it's ready to be committed. I can imagine adding patches that aren't ready for commit, in which case I wouldn't set the flag. As far as doing the commit, I think on Hadoop, the committer just does the svn commit and resolves the Jira issue, w/o changing the assignee. We don't have to do it that way, of course, but I do kinda like it that way. I figure if contributors (as opposed to committers) are the lead on any follow-up discussion, that's a good thing, in terms of load balancing? > Allow QP subclasses to support Wildcard Queries with leading "*" > ---------------------------------------------------------------- > > Key: LUCENE-489 > URL: http://issues.apache.org/jira/browse/LUCENE-489 > Project: Lucene - Java > Issue Type: Wish > Components: QueryParser > Reporter: Peter Schäfer > Assigned To: Otis Gospodnetic > Fix For: 2.1 > > Attachments: LUCENE-489.patch, qp.diff > > > It would be usefull for some users if the logic that prevents QueryParser > from creating WIldcardQueries with leading wildcard characters ("?" or "*") > be moved from the grammer into the base implimentation of getWildcardQuery so > that it may be overridden in subclasses without needing to modifiy the > grammer directly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
