lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuck Williams (JIRA)" <>
Subject [jira] Commented: (LUCENE-558) Selective field loading
Date Thu, 27 Apr 2006 22:02:38 GMT
    [ ] 

Chuck Williams commented on LUCENE-558:

You're right about IndexReader.document(int), although it appears you removed (package api)
FieldsReader.doc(int).  I've been reading the patch file (and now the new files) rather than
applying the patch since it affects some of the same files as another patch of mine (LUCENE-362).

Re. skipChars() do you have a newer version that is not attached?  The version in your patch
file takes, I believe, precisely the same number of instructions as mine.  It's hard to see
how to do it better without changing the index representation (to store byte count instead
of char count for strings, which would require an extra seek to write a string).

545 is a good improvement.  I was initiually put off by the scope of it.  We don't need this
issue (558).  Is there interest in committing 545?

> Selective field loading
> -----------------------
>          Key: LUCENE-558
>          URL:
>      Project: Lucene - Java
>         Type: New Feature

>   Components: Index
>     Versions: 2.0
>  Environment: All
>     Reporter: Chuck Williams
>  Attachments: LuceneTrunk.patch
> Provides a new api, IndexReader.document(int doc, String[] fields).  A document containing
only the specified fields is created.  The other fields of the document are not loaded, although
unfortunately uncompressed strings still have to be scanned because the length information
in the index is for UTF-8 encoded chars and not bytes.  This is useful for applications that
need quick access to a small subset of the fields.  It can be used in conjunction with or
for some uses instead of ParallelReader.
> This is a much smaller change for a simpler use case than Lucene-545.  No existing API's
are affected.
> All the tests pass and new tests are added to verify the feature.

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