Bubbling up newer records

Hi, Is it possible to bubble up newer records in lucene search results? ie.I want Lucene to give a higher score to records which are closer to today's date. -- View this message in context: http://www.nabble.com/Bubbling-up-newer-records-tp21470766p21470766.html Sent from the Lucene - Java Deve

[jira] Updated: (LUCENE-1516) Integrate IndexReader with IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1516: - Attachment: LUCENE-1516.patch Patch includes the latest patch from LUCENE-1314 and is un

[jira] Commented: (LUCENE-1476) BitVector implement DocIdSet

[ https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663903#action_12663903 ] Jason Rutherglen commented on LUCENE-1476: -- I think it should be up to the user.

[jira] Commented: (LUCENE-1476) BitVector implement DocIdSet

[ https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663837#action_12663837 ] Yonik Seeley commented on LUCENE-1476: -- bq. IndexReader.getDeletedDocs that returns a

[jira] Commented: (LUCENE-1476) BitVector implement DocIdSet

[ https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663815#action_12663815 ] Jason Rutherglen commented on LUCENE-1476: -- To simplify the patch, can we agree t

Re: [jira] Closed: (SOLR-954) SolrQuery - better cross-referential documentation / fix inconsistent cross-reference links .

Key, I think we have the practice to keep issues in Fixed state (not Closed). I'm not sure if closing them does any harm or not in terms of JIRA workflow/figuring out what was fixed/reports and such...anyone knows? Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Orig

[jira] Resolved: (LUCENE-1519) Change Primitive Data Types from int to long in class SegmentMerger.java

[ https://issues.apache.org/jira/browse/LUCENE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1519. Resolution: Fixed Fix Version/s: 2.9 Committed revision 734415. Thanks Dee

Re: Question on small optimization in TrieUtils

Right. Keyword and other such fields (likely not analyzed) should def be omitTf and OmitNorms, unless you have some special situation. Uwe Schindler wrote: Yes, that was may opinion when reading the java docs. I wanted to be sure. In principle we could write down somewhere, that disabling norm

RE: Question on small optimization in TrieUtils

Yes, that was may opinion when reading the java docs. I wanted to be sure. In principle we could write down somewhere, that disabling norms is good for not-analyzed fields like document identifiers, numbers, Such a field do not need norms, as e.g. the document identifier is only used for searc

[jira] Commented: (LUCENE-1483) Change IndexSearcher multisegment searches to search each individual segment using a single HitCollector

[ https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663765#action_12663765 ] Michael McCandless commented on LUCENE-1483: I was wondering the same thing.

Re: Question on small optimization in TrieUtils

It shouldn't have an affect, I'd make the change. The norm setting is only respective to the field you set it on, and a sort field won't benefit IMO. Norms are for index time boost and field length normalization right? Turn them off I say. Uwe Schindler wrote: Hi, I was just looking through

[jira] Commented: (LUCENE-1483) Change IndexSearcher multisegment searches to search each individual segment using a single HitCollector

[ https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663761#action_12663761 ] Mark Miller commented on LUCENE-1483: - Any ideas on why ORDSUBORD would beat the polic

Question on small optimization in TrieUtils

Hi, I was just looking through some more optimizations of my trie encoded fields. They are currently indexed using omitTf. Additionally I could also add omitNorms to the index options for such type of fields (because they are only used for sorting and the special TrieRangeFilter). Does this has an

[jira] Commented: (LUCENE-1483) Change IndexSearcher multisegment searches to search each individual segment using a single HitCollector

[ https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663754#action_12663754 ] Michael McCandless commented on LUCENE-1483: I agree, ORDDEM looks overall bes

[jira] Commented: (LUCENE-1519) Change Primitive Data Types from int to long in class SegmentMerger.java

[ https://issues.apache.org/jira/browse/LUCENE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663702#action_12663702 ] Michael McCandless commented on LUCENE-1519: Grr -- the bug is real. I'll fix

[jira] Assigned: (LUCENE-1519) Change Primitive Data Types from int to long in class SegmentMerger.java

[ https://issues.apache.org/jira/browse/LUCENE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-1519: -- Assignee: Michael McCandless > Change Primitive Data Types from int to long in

[jira] Commented: (LUCENE-1519) Change Primitive Data Types from int to long in class SegmentMerger.java

[ https://issues.apache.org/jira/browse/LUCENE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663652#action_12663652 ] Deepak commented on LUCENE-1519: Hi Otis It is a lucene bug. Is there any other mail list