DO NOT REPLY [Bug 35664] - Ordered spanquery with repeated subqueries can fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35664] - Ordered spanquery with repeated subqueries can fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: IndexWriter and system properties

I remember adding some of those, and I don't really recall why I was adding them. I think we just didn't have various setters we have now, and for some reason chose not to add them. Now that we have (most of them?), I think system properties can go. Otis --- Daniel Naber <[EMAIL PROTECTED]> wr

Re: IndexWriter and system properties

From the perspective of a user of Lucene: IMHO, having system properties for a third-party library is not good: 1) System properties are not explicit in the library's api. 2) System properties are applied non-local to the use of a library's api. 3) System properties represents global variables, no

Re: IndexWriter and system properties

On Jul 11, 2005, at 5:56 PM, Daniel Naber wrote: there's a bug report (#34359) asking to catch and ignore access exceptions when reading system properties so Lucene can be used in an applet. I wanted to apply that patch, but now I'm not sure anymore: does it make sense for Lucene to read setti