Module org.elasticsearch.server
Package org.elasticsearch.index.fielddata

Class LongScriptFieldData

java.lang.Object
org.elasticsearch.index.fielddata.IndexNumericFieldData
org.elasticsearch.index.fielddata.LongScriptFieldData
All Implemented Interfaces:
IndexFieldData<LeafNumericFieldData>
public final class LongScriptFieldData extends IndexNumericFieldData

  • Field Details

    • toScriptFieldFactory

      protected final ToScriptFieldFactory<org.apache.lucene.index.SortedNumericDocValues> toScriptFieldFactory

  • Method Details

    • getFieldName

      public String getFieldName()
      Description copied from interface: IndexFieldData
      The field name.

    • getValuesSourceType

      public ValuesSourceType getValuesSourceType()
      Description copied from interface: IndexFieldData
      The ValuesSourceType of the underlying data. It's possible for fields that use the same IndexFieldData implementation to have different ValuesSourceTypes, such as in the case of Longs and Dates.

    • load

      public LongScriptFieldData.LongScriptLeafFieldData load(org.apache.lucene.index.LeafReaderContext context)
      Description copied from interface: IndexFieldData
      Loads the atomic field data for the reader, possibly cached.

    • loadDirect

      public LongScriptFieldData.LongScriptLeafFieldData loadDirect(org.apache.lucene.index.LeafReaderContext context) throws IOException
      Description copied from interface: IndexFieldData
      Loads directly the atomic field data for the reader, ignoring any caching involved.
      Throws:
      IOException

    • getNumericType

      public IndexNumericFieldData.NumericType getNumericType()
      Description copied from class: IndexNumericFieldData
      The numeric type of this number.
      Specified by:
      getNumericType in class IndexNumericFieldData

    • sortRequiresCustomComparator

      protected boolean sortRequiresCustomComparator()
      Description copied from class: IndexNumericFieldData
      Should sorting use a custom comparator source vs. rely on a Lucene SortField. Using a Lucene SortField when possible is important because index sorting cannot be configured with a custom comparator, and because it gives better performance by dynamically pruning irrelevant hits. On the other hand, Lucene SortFields are less flexible and make stronger assumptions about how the data is indexed. Therefore, they cannot be used in all cases.
      Specified by:
      sortRequiresCustomComparator in class IndexNumericFieldData

    • isIndexed

      protected boolean isIndexed()
      Description copied from class: IndexNumericFieldData
      Return true if, and only if the field is indexed with points that match the content of doc values.
      Specified by:
      isIndexed in class IndexNumericFieldData