[
https://issues.apache.org/jira/browse/LUCENE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572768#action_12572768
]
Eric commented on LUCENE-1195:
--
When faceting(iterating all terms), will each term be looked
[
https://issues.apache.org/jira/browse/LUCENE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572753#action_12572753
]
Yonik Seeley commented on LUCENE-1195:
--
Thinking about a common use in Solr: doing a
[
https://issues.apache.org/jira/browse/LUCENE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572750#action_12572750
]
michaelbusch edited comment on LUCENE-1195 at 2/26/08 5:04 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572750#action_12572750
]
Michael Busch commented on LUCENE-1195:
---
Test details:
The index has 500,000 docs an
[
https://issues.apache.org/jira/browse/LUCENE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572747#action_12572747
]
Yonik Seeley commented on LUCENE-1195:
--
Nice results!
I assume this is on a non-optim
That's what I was pointing out. The test is VERY broken
On Feb 26, 2008, at 5:53 PM, Mike Klaas wrote:
On 26-Feb-08, at 3:00 PM, Michael Busch (JIRA) wrote:
50,000 AND queries with 3 terms each:
old: 152 secs
new (with LRU cache): 112 secs (26% faster)
50,000 OR queries
This can only possibly work if all 50,000 terms are held in memory,
otherwise the cache management overhead is going to matter.
What is the number of terms in the database? What is the distribution
of the terms used in the test case (differ for each query)?
Performance tests like this witho
On 26-Feb-08, at 3:00 PM, Michael Busch (JIRA) wrote:
50,000 AND queries with 3 terms each:
old: 152 secs
new (with LRU cache): 112 secs (26% faster)
50,000 OR queries with 3 terms each:
old: 175 secs
new (with LRU cache): 133 secs (24% faster)
For bigger ind
Performance improvement for TermInfosReader
---
Key: LUCENE-1195
URL: https://issues.apache.org/jira/browse/LUCENE-1195
Project: Lucene - Java
Issue Type: Improvement
Components: Index
[
https://issues.apache.org/jira/browse/LUCENE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-1187:
-
Attachment: javadocsZero2Match.patch
Attached javadocsZero2Match.patch that replaces the last fe
[
https://issues.apache.org/jira/browse/LUCENE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572637#action_12572637
]
Michael McCandless commented on LUCENE-1194:
{quote}
When autoCommit is true,
[
https://issues.apache.org/jira/browse/LUCENE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572576#action_12572576
]
Ning Li commented on LUCENE-1194:
-
Great to see deleteByQuery being added to IndexWriter!
[
https://issues.apache.org/jira/browse/LUCENE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Falca closed LUCENE-1192.
--
Tried last option:
{quote}
* Close the ramIndexWriter before passing its directory to
addIndexe
[
https://issues.apache.org/jira/browse/LUCENE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1194:
---
Attachment: LUCENE-1194.patch
Attached patch. All tests pass.
> Add deleteByQuery
Add deleteByQuery to IndexWriter
Key: LUCENE-1194
URL: https://issues.apache.org/jira/browse/LUCENE-1194
Project: Lucene - Java
Issue Type: New Feature
Reporter: Michael McCandless
Ass
[
https://issues.apache.org/jira/browse/LUCENE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572495#action_12572495
]
Michael McCandless commented on LUCENE-1192:
You're welcome!
> FileNotFound e
[
https://issues.apache.org/jira/browse/LUCENE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1192.
Resolution: Invalid
> FileNotFound exception on adding a RAMDirectory to an IndexW
[
https://issues.apache.org/jira/browse/LUCENE-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1184.
Resolution: Fixed
I just committed this. Thanks Tim!
> Allow SnapshotDeletionPol
OOM exception while sorting on more than 1 field
Key: LUCENE-1193
URL: https://issues.apache.org/jira/browse/LUCENE-1193
Project: Lucene - Java
Issue Type: Bug
Components: Search
[
https://issues.apache.org/jira/browse/LUCENE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572457#action_12572457
]
Alex Falca commented on LUCENE-1192:
Thanks for the explanations and proposed ways to
[
https://issues.apache.org/jira/browse/LUCENE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572449#action_12572449
]
Michael McCandless commented on LUCENE-1192:
This actually isn't quite a vali
[
https://issues.apache.org/jira/browse/LUCENE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Falca updated LUCENE-1192:
---
Description:
Hi,
I'm getting FileNotFoundException on adding RAMDirectory to an IndexWriter with
f
FileNotFound exception on adding a RAMDirectory to an IndexWriter
-
Key: LUCENE-1192
URL: https://issues.apache.org/jira/browse/LUCENE-1192
Project: Lucene - Java
Issue Type: Bu
23 matches
Mail list logo