Indexes: Storing Data in Index

Once the tokenization and analysis process is completed, the resulting tokens, created according to the used analyzer, are stored in the index. By default, tokens saved in the index are available for searching. but their original field values aren't stored.

Lucene allows you to store the original field text (before it is analyzed) as well. This feature is exposed in the index definition object as the Storage property of the IndexFieldOptions.

Enabling field storing causes original values will be available for retrieval when doing projections.

class Employees_ByFirstAndLastName extends AbstractIndexCreationTask {
    constructor() {
        = `docs.Employees.Select(employee => new {    
            FirstName = employee.FirstName,    
            LastName = employee.LastName
        })`;"FirstName", "Yes");"LastName", "Yes");
const indexDefinition = new IndexDefinition(); = "Employees_ByFirstAndLastName";
indexDefinition.maps = new Set([
    "docs.Employees.Select(employee => new {" +
    "    FirstName = employee.FirstName," +
    "    LastName = employee.LastName" +
indexDefinition.fields = {
    "FirstName": { storage: "Yes" },
    "LastName": { storage: "Yes" }

await store.maintenance.send(new PutIndexesOperation(indexDefinition));



Default Storage value for each field is "No". Keep in mind that storing fields will increase disk space usage.


If the projection requires only the fields that are stored, then the document will not be loaded from the storage and the query results will come directly from the index. This can increase query performance at the cost of disk space used.