RE: about numeric range searching with large value sets patches

My fault, I forgot to attach it. I've added it now. Let me know how this works for you. Randy Puttick -Original Message- From: Antoine Brun [mailto:[EMAIL PROTECTED] Sent: Friday, August 19, 2005 8:11 AM To: java-dev@lucene.apache.org Subject: about numeric range searching with

RE: Developper Question - Highlighting

Actually, it's a very small tweak to the Field class to permit Reader values other than through the Text helper function. DocumentWriter (which actually extracts and tokenizes the field data doesn't care about the artificial restriction in Field). Randy -Original Message- From: Adity

RE: [newbie]problem about range query

I recently submitted a patch that replaces the implementation for multi-term queries (used for fuzzy and wildcard queries) with an implementation that does the union through a priority queue (these are always disjunctions). You *COULD* mimic this change to replace the mechanism used for range quer

[jira] Updated: (LUCENE-421) Numeric range searching with large value sets

[ http://issues.apache.org/jira/browse/LUCENE-421?page=all ] Randy Puttick updated LUCENE-421: - Attachment: FloatRangeScorer.java IntegerRangeScorer.java Fix for the bug found by IntegerRangeQueryTest > Numeric range searching w

[jira] Created: (LUCENE-517) norm compression breaks ranking for small fields

: N/A Reporter: Randy Puttick The scheme of compressing document norms to one byte loses a lot of information. This completely breaks search ranking on small fields because there is no way to see the difference between documents with shorter and longer fields that contain the same number of

[jira] Created: (LUCENE-518) document field lengths count analyzer synonym overlays

Environment: N/A Reporter: Randy Puttick Using a synonym expansion analyzer to add tokens with zero offset from the substituted token should not extend the length of the field in the document (for scoring purposes) -- This message is automatically generated by JIRA. - If you think it was sent

[jira] Commented: (LUCENE-518) document field lengths count analyzer synonym overlays

[ http://issues.apache.org/jira/browse/LUCENE-518?page=comments#action_12369918 ] Randy Puttick commented on LUCENE-518: -- What you say would make sense if you thought that queries would contain several synonyms. All my experience says that they don&#

[jira] Commented: (LUCENE-517) norm compression breaks ranking for small fields

[ http://issues.apache.org/jira/browse/LUCENE-517?page=comments#action_12369936 ] Randy Puttick commented on LUCENE-517: -- Thanks Yorik, this could work for my purposes; it'd be nice to have a choice on a per-field basis don't you thin

[jira] Created: (LUCENE-524) Current implementation of fuzzy and wildcard queries inappropriately implemented as Boolean query rewrites

-524 Project: Lucene - Java Type: Improvement Components: Search Versions: 1.9 Reporter: Randy Puttick The implementation of MultiTermQuery in terms of BooleanQuery introduces several problems: 1) Collisions with maximum clause limit on boolean queries which throws

[jira] Updated: (LUCENE-524) Current implementation of fuzzy and wildcard queries inappropriately implemented as Boolean query rewrites

[ http://issues.apache.org/jira/browse/LUCENE-524?page=all ] Randy Puttick updated LUCENE-524: - Attachment: MultiTermQuery.java MultiTermScorer.java Implements union operation on a priority queue and scores multi-term based on maximum