You're welcome! Mike McCandless
http://blog.mikemccandless.com On Fri, Sep 4, 2015 at 11:07 AM, [email protected] <[email protected]> wrote: > Thanks for this Mike :-) > > On Fri, Sep 4, 2015 at 11:02 AM Michael McCandless <[email protected]> wrote: >> >> Lucene summary for this week: >> >> A 5.3.1 bugfix release may be coming soon >> >> See the confusion matrix for a classifier >> >> Remove a nasty classloader hack that broke MorfologikFilter , and fix it >> correctly so you can pass the dictionary as a URI >> >> The new BoostQuery decouples Query from boosting, but it was missing its >> rewrite method >> >> How can we compress postings payloads? >> >> Nested conjunctions should always be flattened >> >> MultiCollector did not handle early termination properly >> >> Add a point-within-distance query implemented with BKD trees >> >> Speed up IndexSearcher.count when a query is so simple (match all, single >> term) that we can use index statistics instead >> >> The integration of BKDTree and Geo3D is done (for Lucene 5.4.0), providing >> accurate and fast earth-surface "point in shape" queries, but we need to >> make its randomized tests more evil by simulating planets more squashed than >> earth, requiring somecrazy math, including Lagrange multipliers >> >> GeoPointDistanceQuery is buggy with large distances >> >> Don't use approximations for MatchAllDocsQuery, and give it a dedicated >> BulkScorer >> >> Dodge bugs in Java's collators >> >> Windows NTFS pending delete state for a file causes assertion failures in >> Lucene; we should fix Lucene's WindowsFS to also simulate this state >> >> Symlinks to an index directory continue to cause problems for users >> >> CheckIndex cannot handle corrupt .si files >> >> Reduce heap used by CompressingStoredFieldsWriter when writing large >> strings during indexing >> >> Reduce heap used by the new geo point queries by building the BytesRef on >> demand for sub-ranges >> >> GeoPointDistanceRangeQuery will match points within a min/max distance >> range >> >> When you incorrectly index nested documents the resulting error messages >> are very confusing >> >> DisjunctionMaxQuery, BoostingQuery and BoostedQuery now use IndexSearcher >> to create sub-weights so caching can apply >> >> Mike McCandless > > -- > Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > http://www.solrenterprisesearchserver.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
