cutting 2004/03/29 15:40:31
Modified: xdocs fileformats.xml
Log:
Removed outdated limitations.
Revision Changes Path
1.10 +0 -25 jakarta-lucene/xdocs/fileformats.xml
Index: fileformats.xml
===================================================================
RCS file: /home/cvs/jakarta-lucene/xdocs/fileformats.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fileformats.xml 29 Mar 2004 22:30:40 -0000 1.9
+++ fileformats.xml 29 Mar 2004 23:40:31 -0000 1.10
@@ -1252,32 +1252,7 @@
probably will be. These should therefore be replaced with either
UInt64 values, or better yet, with VInt values which have no limit.
</p>
- <p>There
- are only two places where the code requires that a value be fixed
- size. These are:
- </p>
- <ol>
- <li><p>
- The FieldValuesPosition (in the stored field index file,
.fdx).
- This already uses a UInt64, and so is not a problem.
- </p></li>
- <li><p>The
- TermCount (in the term info file, .tis). This is written
last but
- is read when the file is first opened, and so is stored at
the
- front. The indexing code first writes an zero here, then
overwrites
- it after the rest of the file has been written. So unless
this is
- stored elsewhere, it must be fixed size and should be
changed to a
- UInt64.
- </p>
- </li>
- </ol>
- <p>Other
- than these, all UInt values could be converted to VInt to remove
- limitations.
- </p>
- <p><br/><br/>
- </p>
</section>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
