| clear query|facets|time |
Search criteria: TermQParserPlugin.
Results from 71 to 80 from
322 (3.885s).
|
|
|
Loading phrases to help you
refine your search...
|
|
Re: inconsistency/performance trap of empty terms - Lucene - [mail # dev]
|
|
...On Sat, Oct 30, 2010 at 12:51 PM, DM Smith wrote: you have to also wrap the string in a reader, call Tokenizer.reset(Reader), and call reset() on the entire chain [unless in a me...
|
|
|
Author: Robert Muir,
2010-10-30, 17:16
|
|
|
Re: inconsistency/performance trap of empty terms - Lucene - [mail # dev]
|
|
... current or future support for s uch null queries? in a database, not having a value for field X is 'null'. 1. null is different than empty term. 2. comparing this concept with an inverted index...
|
|
... vs a database record really isn't a comparison. by not having 'empty' terms (terms of length=0), what searches would be affected. I still haven't heard a real use case (though surely...
|
|
|
Author: Robert Muir,
2010-10-29, 00:49
|
|
|
Re: inconsistency/performance trap of empty terms - Lucene - [mail # dev]
|
|
...On Sat, Oct 30, 2010 at 11:40 AM, Earwin Burrfoot wrote: i agree (for the indexer), but a lot of people like to use the QueryParser.... so we need a "tokenstream-factory" of some...
|
|
|
Author: Robert Muir,
2010-10-30, 15:43
|
|
|
Re: inconsistency/performance trap of empty terms - Lucene - [mail # dev]
|
|
...On Sat, Oct 30, 2010 at 9:00 AM, Earwin Burrfoot wrote: +1. This is confusing and comes up often on the user list. The way I think it happens is like this: Joe Schmoe, like...
|
|
|
Author: Robert Muir,
2010-10-30, 13:14
|
|
|
Re: inconsistency/performance trap of empty terms - Lucene - [mail # dev]
|
|
... for the empty term that you have found (because i can't think of a use case, except making your search engine slower!) ...
|
|
|
Author: Robert Muir,
2010-10-29, 00:20
|
|
|
inconsistency/performance trap of empty terms - Lucene - [mail # dev]
|
|
...Hello, Mike and I were discussing some very unrelated stuff and the question of how to handle the empty term came up... I started thinking about this email: http...
|
|
...://www.lucidimagination.com/search/document/a8d3a8647e581a5b/patternreplacefilterfactory_creating_empty_string_as_a_term#f43d167b91c2ba07 So, looking through the analyzers, I think we should make a decision about what to do with empty...
|
[+ show more]
[- hide]
| ... terms. In my opinion there is a performance trap here, that might work like this: 1. a user, particularly say a solr user is using a combination of tokenizers/filters and ends out... |
| ... with the "empty term" as basically a mega-stopword, like what happened to that user. 2. due to this, their queries have terrible performance, especially if they are 'auto-generating phrase queries' (the... |
| ... solr default) 3. but, its not possible that anyone can really even rely upon the analyzers handling empty terms correctly, because we are so inconsistent about it. Just taking a quick glance... |
|
|
Author: Robert Muir,
2010-10-27, 10:29
|
|
|
Re: Lucene3xCodec doesn't allow deletions in 4x? - Lucene - [mail # dev]
|
|
.../test-framework/src/java/org/apache/lucene/codecs/lucene3x/PreFlexRWCodec.java (working copy) @@ -38,8 +38,6 @@ private final TermVectorsFormat termVectors = new PreFlexRWTermVectorsFormat(); private final SegmentInfoFormat segment...
|
|
...Directory(oldIndexDirs.get(name)); + IndexWriter iw = new IndexWriter(dir, new IndexWriterConfig(TEST_VERSION_CURRENT, null)); + iw.deleteDocuments(new Term("id", "3")); + iw.close(); + IndexReader ir = Directory...
|
|
|
Author: Robert Muir,
2012-08-29, 03:01
|
|
|
Re: [JENKINS] Lucene-Solr-4.x-Linux (64bit/ibm-j9-jdk6) - Build # 863 - Failure! - Lucene - [mail # dev]
|
|
...IOUtils, TestPositionIncrement, TestIndexInput, TestFuzzyQuery , TestCollectionUtil, TestBasicOperations, TestForceMergeForever, Nested, N ested, TestPrefixCodedTerms, TestNRTReaderWithThreads, Nested1...
|
|
|
Author: Robert Muir,
2012-09-04, 23:29
|
|
|
public classes with no class javadocs whatsoever - Lucene - [mail # dev]
|
|
...] build/docs/queryparser/org/apache/lucene/queryparser/surround/query/package-summary.html [exec] missing: DistanceSubQuery [exec] missing: SimpleTerm.MatchingTermVisitor [exec...
|
|
...Query [exec] missing: OrQuery [exec] missing: SimpleTerm [exec] missing: SpanNearClauseFactory [exec] missing: SrndPrefixQuery [exec] missing: SrndQuery [exec...
|
[+ show more]
[- hide]
| ...] missing: SrndTermQuery [exec] missing: SrndTruncQuery [exec] missing: TooManyBasicQueries [exec] [exec] build/docs... |
| ...QueryBuilder [exec] missing: BooleanFilterBuilder [exec] missing: BooleanQueryBuilder [exec] missing: BoostingQueryBuilder [exec] missing: BoostingTermBuilder [exec] missing... |
| ...NearBuilder [exec] missing: SpanNotBuilder [exec] missing: SpanOrBuilder [exec] missing: SpanOrTermsBuilder [exec] missing: SpanQueryBuilderFactory [exec] missing: SpanTerm... |
|
|
Author: Robert Muir,
2012-08-17, 13:39
|
|
|
Re: Improve OOTB behavior: English word-splitting should default to autoGeneratePhraseQueries=true - Lucene - [mail # dev]
|
|
...On Wed, Aug 8, 2012 at 11:43 PM, Chris Hostetter wrote: Can you honestly generalize this rule from "how to handle hyphen" to "if > 1 term comes out of a whitespace-separated term...
|
|
|
Author: Robert Muir,
2012-08-09, 03:59
|
|
|
|
