Mike - thanks for explanation, it makes perfect sense!
Otis
- Original Message
From: Michael McCandless <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Thursday, April 5, 2007 8:03:44 PM
Subject: Re: [jira] Commented: (LUCENE-843) improve how IndexWriter uses RAM to
buffer ad
CH CH CH CH CH CHANGES.txt, no?
Please see: https://issues.apache.org/jira/browse/LUCENE-857#action_12487433
Otis
- Original Message
From: Peter Keegan <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Friday, April 6, 2007 8:38:49 AM
Subject: Re: Caching in QueryFilter - why?
>t
[
https://issues.apache.org/jira/browse/LUCENE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487433
]
Otis Gospodnetic commented on LUCENE-857:
-
I think this is where a javadoc and CHANGES.txt come in. People w
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487432
]
Otis Gospodnetic commented on LUCENE-584:
-
Doron, thanks for jumping on this!
1. I thought I'd see better pe
I'd advise against calling optimize() at all in an environment whose indices
are constantly updated. That's what mergeFactor helps with. Keep it low, and
Lucene itself will regularly merge segments more often. If one still wants to
call optimize(), you'd want to know how long it would take on
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487431
]
Doron Cohen commented on LUCENE-584:
One line was cut out - here are the four lines again
Operation ro
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-584:
---
Attachment: bench-diff.txt
The benchmark does not search with filters. Is any speedup still expected?
See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/47/
--
[...truncated 1585 lines...]
AUsrc/java/org/apache/lucene/document/Document.java
AUsrc/java/org/apache/lucene/document/package.html
A src/java/org/apache/lucene/
On Saturday 07 April 2007 00:42, Chris Hostetter wrote:
> : I think you can put in the link, just use relative link like in the
> : site.xml.
>
> using a relative link is *key* ... it ensures not only that the static
> files build by the nightly build work, but also that the docs
> distributed wit
I think this is great, and it gave me an idea. What if another thread could
call a "stop optimize" which would stop the optimize after it came to a
consistent state (not in the middle of a segment merge).
We schedule our optimizes for the "lull" time period, but with 24/7 operation
this could b
10 matches
Mail list logo