lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Smith (JIRA)" <>
Subject [jira] Updated: (LUCENE-1810) Add a LATENT FieldSelectorResult
Date Mon, 17 Aug 2009 17:38:14 GMT


Tim Smith updated LUCENE-1810:

    Attachment: LUCENE-1810.patch

Attaching patch to provide FieldSelectorResult.LATENT

this patch hooks in to add a "cacheResult" flag to LazyField

LOAD_LAZY sets this flag to true
LATENT sets this flag to false

added test that verifies stringValue() returned from LAZY_LOAD is always the same, and stringValue()
returned from LATENT is always different (reloaded each time)

> Add a LATENT FieldSelectorResult
> --------------------------------
>                 Key: LUCENE-1810
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Wish
>          Components: Search
>    Affects Versions: 2.4
>            Reporter: Tim Smith
>         Attachments: LUCENE-1810.patch
> I propose adding LATENT FieldSelectorResult
> this would be similar to LAZY_LOAD except that it would NEVER cache the stored value
> This will be useful for very large fields that should always go direct to disk (because
they will take so much memory)
> when caching Documents returned from a Searcher, the large field may be initially requested
as LAZY_LOAD, however once someone reads this field, it will then get locked into memory.
if this Document (and others like it) are cached, it can start to use a very large amount
of memory for these fields
> Contract for FieldSelectorResult.LATENT should be that it will always be pulled direct
from the IndexInput and never be persisted in memory as part of a Fieldable
> I could prepare a patch if desired

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message