[
https://issues.apache.org/jira/browse/LUCENE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-837:
---
Attachment: benchmark-updates.patch
See changes.txt in contrib/benchmark.
Patch applies in c
[
https://issues.apache.org/jira/browse/LUCENE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-837:
---
Summary: contrib/benchmark QueryMaker and Task Refactorings (was:
QueryMaker Implementations
[
https://issues.apache.org/jira/browse/LUCENE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482292
]
Hoss Man commented on LUCENE-446:
-
I just remembered one of the reasons why i didn't do this the last time i
looked
QueryMaker Implementations
--
Key: LUCENE-837
URL: https://issues.apache.org/jira/browse/LUCENE-837
Project: Lucene - Java
Issue Type: Bug
Components: contrib/benchmark
Reporter: Grant Ingersoll
[
https://issues.apache.org/jira/browse/LUCENE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482281
]
Hoss Man commented on LUCENE-446:
-
I'm in favor ... i think once upon a time Yonik held off because he wasn't sure
i
: It doesn't apply to SVN head just yet (I need to update the payloads
: commit -- Michael: you returned the favor here!), it's not yet thread friendly
: (though I can do that after first patch), it messes up the merge policy
: when you flush by RAM and not by document count (this is actually alre
robert engels wrote:
but a better solution, since you probably need a indexed file into the
terms file, you might not even need the term count, since you should
read the indexed file into memory anyway (read every 16 entries, etc.) -
at which point you will know the number of terms in the file.
but a better solution, since you probably need a indexed file into
the terms file, you might not even need the term count, since you
should read the indexed file into memory anyway (read every 16
entries, etc.) - at which point you will know the number of terms in
the file.
On Mar 19, 20
write the term count at the end of the file, uncompressed
On Mar 19, 2007, at 6:13 PM, Matt Chaput wrote:
Hi all!
I'm reimplementing a very Lucene-like search library as a learning
experience and I've run into a snag. Before I go deep code diving,
I thought I'd ask here in case someone has
Hi all!
I'm reimplementing a very Lucene-like search library as a learning
experience and I've run into a snag. Before I go deep code diving, I
thought I'd ask here in case someone has the time to answer.
The term dictionary file includes the term count in a header. But when
I'm merging segm
"Marvin Humphrey" <[EMAIL PROTECTED]> wrote:
> > I think some of these changes are similar to how KinoSearch builds a
> > segment.
>
> Yup... sounds familiar. ;)
>
> > I'm still working through some lingering issues before I can make a
> > clean patch,
>
> Well, where is it? Don't keep it a
Woops! I meant for this to go to java-dev...
Mike
On Mon, 19 Mar 2007 08:09:37 -0400, "Michael McCandless" <[EMAIL PROTECTED]>
said:
> Hi,
>
> I've been looking into improving performance of IndexWriter,
> specifically how it makes use of RAM to buffer added documents.
>
> I've created a new
Hi,
I have a Lucene implementation which works good (I thought), but after a day
(or few days) I don't get search results anymore and in the logs i see this
error:
doc counts differ for segment _qsl: fieldsReader shows 10 but segmentInfo
shows 100
But I've done noting with the index. does anyon
13 matches
Mail list logo
