Details

    • Wish
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.4
    • 3.1, 4.0-ALPHA
    • core/search
    • None
    • New

    Description

      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

      Attachments

        1. LUCENE-1810.patch
          11 kB
          Grant Ingersoll
        2. LUCENE-1810.patch
          16 kB
          Tim Smith

        Activity

          People

            gsingers Grant Ingersoll
            tsmith Tim Smith
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment