lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <>
Subject [jira] Commented: (LUCENE-756) Maintain norms in a single file .nrm
Date Thu, 21 Dec 2006 18:48:22 GMT
    [ ] 
Doug Cutting commented on LUCENE-756:

Since we're adding a new file, shouldn't we give it a header, so that it's format can be revised?
 Something like:
  new byte[] {'N','R','M',VERSION}
as the first four bytes.  We might someday decide to change the representation used, e.g.,
a different one-byte-float format, or permit higher resolution, or compression, or somesuch.

Also, should we use a constant for ".nrm" extension, so that it's checked at compile-time?

> 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: 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