[jira] Commented: (LUCENE-1340) Make it posible not to include TF information in index

[ https://issues.apache.org/jira/browse/LUCENE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618069#action_12618069 ] Eks Dev commented on LUCENE-1340: - that sound like consensus :) Great! in that case LUCEN

[jira] Commented: (LUCENE-1340) Make it posible not to include TF information in index

[ https://issues.apache.org/jira/browse/LUCENE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618001#action_12618001 ] Doug Cutting commented on LUCENE-1340: -- > I firmly believe there is a way to do inter

[jira] Commented: (LUCENE-1340) Make it posible not to include TF information in index

[ https://issues.apache.org/jira/browse/LUCENE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617996#action_12617996 ] Grant Ingersoll commented on LUCENE-1340: - Yeah, it's one of my biggest regrets in

[jira] Commented: (LUCENE-1340) Make it posible not to include TF information in index

[ https://issues.apache.org/jira/browse/LUCENE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617978#action_12617978 ] Eks Dev commented on LUCENE-1340: - ouch! it is kind of getting personal between me and Fie

RE: Deadlock when multi-threading DocumentsWriter

Looks like, I can never run into that situation. Another doc-id would not even be assigned before flushing out the current doc. From: Jagadesh Nomula [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2008 2:43 PM To: java-dev@lucene.apache.org Subject: RE: Deadloc

[jira] Updated: (LUCENE-1345) Allow Filter as clause to BooleanQuery

[ https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eks Dev updated LUCENE-1345: Attachment: OpenBitSetIteratorExperiment.java TestIteratorPerf.java I just enhanced TestIt

RE: Deadlock when multi-threading DocumentsWriter

Hi Mike, Thanks for the comments. Diagnosing, the stack trace the following statements, might run into a nested lock. org.apache.lucene.index.DocumentsWriter.pauseAllThreads(DocumentsWriter.java:507) org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:2670) The doFlush method

[jira] Updated: (LUCENE-1345) Allow Filter as clause to BooleanQuery

[ https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Elschot updated LUCENE-1345: - Attachment: DisjunctionDISI.java DisjunctionDisi.java of 20080729 has a first try of switching

[jira] Commented: (LUCENE-1340) Make it posible not to include TF information in index

[ https://issues.apache.org/jira/browse/LUCENE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617954#action_12617954 ] Grant Ingersoll commented on LUCENE-1340: - I note a change to Fieldable... sigh..

Sort suggestion

Guys. I've noticed many having trouble with sorting and OOM. Eventually they solve it by throwing more memory at the problem. Should'nt a solution which can sort on disk when neccessary be implemented in core Lucene ? Something like this: http://www.codeodor.com/index.cfm/2007/5/10/Sorting-really

Re: Sort suggestion

The problem isn't sorting per-se... the problem is quickly retrieving the sort value for a document. For that, we currently have the FieldCache that's what takes up the memory. There are more memory efficient ways, but they just haven't been implemented yet. -Yonik On Tue, Jul 29, 2008 at 3:

[jira] Issue Comment Edited: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ https://issues.apache.org/jira/browse/LUCENE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617880#action_12617880 ] mmastrac edited comment on LUCENE-753 at 7/29/08 10:58 AM: --

[jira] Issue Comment Edited: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ https://issues.apache.org/jira/browse/LUCENE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617880#action_12617880 ] mmastrac edited comment on LUCENE-753 at 7/29/08 10:57 AM: --

[jira] Commented: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ https://issues.apache.org/jira/browse/LUCENE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617880#action_12617880 ] Matthew Mastracci commented on LUCENE-753: -- I just tried out the latest NIOFSDirec

[jira] Commented: (LUCENE-1345) Allow Filter as clause to BooleanQuery

[ https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617836#action_12617836 ] Eks Dev commented on LUCENE-1345: - bq. comparison with -1 is being optimized away entirely

[jira] Commented: (LUCENE-1345) Allow Filter as clause to BooleanQuery

[ https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617822#action_12617822 ] Yonik Seeley commented on LUCENE-1345: -- bq. I have tried it on long values and this

[jira] Commented: (LUCENE-1345) Allow Filter as clause to BooleanQuery

[ https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617726#action_12617726 ] Eks Dev commented on LUCENE-1345: - Yonik, this would probably work fine for int values (on

Re: [jira] Commented: (LUCENE-1345) Allow Filter as clause to BooleanQuery

as a matter of fact, you can, keeping literals on left hand side prevents some ugly accidental assignments, so at the end of day you have more time to speed things up instead of chasing bugs :) cheers Hoss, god to see you are following this - Original Message > From: Chris Hostetter