On Wednesday 02 March 2005 12:25, Erik Hatcher wrote:
I agree that the current behavior is awkward. Is it worth breaking backwards compatibility to correct this with the patch applied?
I'd vote for fixing this as long as the current QueryParser is still available in Lucene core, maybe as OldQueryParser or NoPrecedenceQueryParser. It's surely better to fix it for 2.0 than for 2.x.
+1. Fixing operator precedence seems to me like an acceptable incompatibility. The change needs to be well documented in release notes, and the old QueryParser should be available, deprecated, for a time for back-compatibility.
Doug
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
