Stored field values in index?
See original GitHub issueI was hoping to reduce the footprint of my index by not storing the original values. I tried the ‘memory’ preset but I still see the large blocks of text I indexed in the output generated by export(). Is there any way to tell FlexSearch not to store the original values.
Also, is there documentation available for the options that FlexSearch.create takes? I’m not understanding things like depth
, threshold
, encode
, etc and was wondering if there is any discussion of them somewhere.
Thanks for an awesome JavaScript library!
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
store | Elasticsearch Guide [8.5] | Elastic
By default, field values are indexed to make them searchable, but they are not stored. This means that the field can be queried,...
Read more >Define Stored Source Fields in Your Atlas Search Index
Learn how to store certain fields in Atlas Search to improve query ... The storedSource option takes a boolean value or an object...
Read more >How to get field data in search results - dtSearch Support
To see the fields in an index, click the "fields" button in the dtSearch Desktop Search dialog box, or click Index > List...
Read more >Create and use an index to improve performance
An index stores the location of records based on the field or fields that you choose to index. After Access obtains the location...
Read more >Elasticsearch _source, doc_values and store Performance
Stored fields have the purpose to store the value of the fields (without any analysis) in order to retrieve them at query time....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The next update will provide a new field “store” in the document descriptor which separates storing from indexing.
I take it back, it is working! Thanks for your help @ts-thomas