Re: svn commit: r689978 - in /lucene/solr/trunk: CHANGES.txt src/java/org/apache/solr/search/SolrQueryParser.java src/java/org/apache/solr/search/WildcardFilter.java src/test/org/apache/solr/Converted

2008-08-29 Thread Chris Hostetter
Are we really sure we want to do this w/o making it configurable on the QParser? (ala: SOLR-218) Unless I'm missing something this change breaks back compatibility of for users who highlight wildcard queries. As i recall: we even have users who force their prefix queries to be wildcards by

Re: svn commit: r689978 - in /lucene/solr/trunk: CHANGES.txt src/java/org/apache/solr/search/SolrQueryParser.java src/java/org/apache/solr/search/WildcardFilter.java src/test/org/apache/solr/Converted

2008-08-29 Thread Yonik Seeley
On Fri, Aug 29, 2008 at 12:18 PM, Chris Hostetter [EMAIL PROTECTED] wrote: Are we really sure we want to do this w/o making it configurable on the QParser? (ala: SOLR-218) I thought about that, but these expanding term queries that have no bounds are really broken... people who depend on them

Re: svn commit: r689978 - in /lucene/solr/trunk: CHANGES.txt src/java/org/apache/solr/search/SolrQueryParser.java src/java/org/apache/solr/search/WildcardFilter.java src/test/org/apache/solr/Converted

2008-08-29 Thread Chris Hostetter
: fire. Imagine everything working fine for months, docs being : occasionally added, until *boom* a magic limit is hit. : : I wouldn't be opposed to a config option I guess... but I think the : default should be something that doesn't unpredictably break (so it : still wouldn't be 100% back