Class PlannerSettings

java.lang.Object
org.elasticsearch.xpack.esql.planner.PlannerSettings

public class PlannerSettings extends Object
Values for cluster level settings used in physical planning.
  • Field Details

    • DEFAULT_DATA_PARTITIONING

      public static final Setting<DataPartitioning> DEFAULT_DATA_PARTITIONING
    • VALUES_LOADING_JUMBO_SIZE

      public static final Setting<ByteSizeValue> VALUES_LOADING_JUMBO_SIZE
    • LUCENE_TOPN_LIMIT

      public static final Setting<Integer> LUCENE_TOPN_LIMIT
    • INTERMEDIATE_LOCAL_RELATION_MAX_SIZE

      public static final Setting<ByteSizeValue> INTERMEDIATE_LOCAL_RELATION_MAX_SIZE
  • Constructor Details

  • Method Details

    • defaultDataPartitioning

      public DataPartitioning defaultDataPartitioning()
    • valuesLoadingJumboSize

      public ByteSizeValue valuesLoadingJumboSize()
    • luceneTopNLimit

      public int luceneTopNLimit()
      Maximum LIMIT that we're willing to push to Lucene's topn.

      Lucene's topn code was designed for search which typically fetches 10 or 30 or 50 or 100 or 1000 documents. That's as many you want on a page, and that's what it's designed for. But if you go to, say, page 10, Lucene implements this as a search for page_size * page_number docs and then materializes only the last page_size documents. Traditionally, Elasticsearch limits that page_size * page_number which it calls the "result window". So! ESQL defaults to the same default - 10,000.

    • intermediateLocalRelationMaxSize

      public ByteSizeValue intermediateLocalRelationMaxSize()