lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Jain (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8671) Add setting for moving FST offheap/onheap
Date Fri, 22 Feb 2019 23:21:00 GMT


Ankit Jain commented on LUCENE-8671:

bq. Ankit Jain We could maybe add a setter on BlockTreeTermsWriter?  And it'd write that setting
into the index, and BlockTreeTermsReader would read that and then load FSTs on or off heap.

[~mikemccand] This sounds pretty good, except that setting is write time. Isn't there a way
to make this read time setting? If not, isn't making this system property a better option?
Though, I'm happy to go with BlockTreeTermsWriter approach if nobody has better suggestion.
Maybe [~jpountz] has any ideas.

> Add setting for moving FST offheap/onheap
> -----------------------------------------
>                 Key: LUCENE-8671
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/FSTs, core/store
>            Reporter: Ankit Jain
>            Priority: Minor
>         Attachments: offheap_generic_settings.patch, offheap_settings.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> While LUCENE-8635, adds support for loading FST offheap using mmap, users do not have
the  flexibility to specify fields for which FST needs to be offheap. This allows users to
tune heap usage as per their workload.
> Ideal way will be to add an attribute to FieldInfo, where we have put/getAttribute. Then
FieldReader can inspect the FieldInfo and pass the appropriate On/OffHeapStore when creating
its FST. It can support special keywords like ALL/NONE.

This message was sent by Atlassian JIRA

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

View raw message