lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <>
Subject [jira] Commented: (LUCENE-756) Maintain norms in a single file .nrm
Date Tue, 16 Jan 2007 19:34:27 GMT


Doron Cohen commented on LUCENE-756:

Michael, I like this improvement!

(At first I considered adding such FORMAT level but decided that it is not worth it, - aiming
backwards compatibility with pre-lockless indexes. Then I had to add that file check - wrong
trade-off indeed.)

Two minor comments:
- getHasMergedNorms() is private and now the method has no logic - I would remove that method
and refer to hasMergedNorms instead.
- the term "merged" (in hasMergedNorms) is a little overloaded with other semantics (in Lucene),
though I cannot think of other matching descriptive (short) term.

Thanks for improving this,

> Maintain norms in a single file .nrm
> ------------------------------------
>                 Key: LUCENE-756
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Doron Cohen
>         Assigned To: Doron Cohen
>            Priority: Minor
>         Attachments:,, LUCENE-756-Jan16.patch,
LUCENE-756-Jan16.Take2.patch, nrm.patch.2.txt, nrm.patch.3.txt, nrm.patch.txt
> Non-compound indexes are ~10% faster at indexing, and perform 50% IO activity comparing
to compound indexes. But their file descriptors foot print is much higher. 
> By maintaining all field norms in a single .nrm file, we can bound the number of files
used by non compound indexes, and possibly allow more applications to use this format.
> More details on the motivation for this in:
(in particular

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message