Class PlannerSettings
java.lang.Object
org.elasticsearch.xpack.esql.planner.PlannerSettings
Values for cluster level settings used in physical planning.
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final Setting<DataPartitioning> static final Setting<ByteSizeValue> static final Setting<ByteSizeValue> -
Constructor Summary
ConstructorsConstructorDescriptionPlannerSettings(ClusterService clusterService) Ctor for prod that listens for updates from theClusterService.PlannerSettings(DataPartitioning defaultDataPartitioning, ByteSizeValue valuesLoadingJumboSize, int luceneTopNLimit, ByteSizeValue intermediateLocalRelationMaxSize) Ctor for testing. -
Method Summary
Modifier and TypeMethodDescriptionintMaximumLIMITthat we're willing to push to Lucene's topn.
-
Field Details
-
DEFAULT_DATA_PARTITIONING
-
VALUES_LOADING_JUMBO_SIZE
-
LUCENE_TOPN_LIMIT
-
INTERMEDIATE_LOCAL_RELATION_MAX_SIZE
-
-
Constructor Details
-
PlannerSettings
Ctor for prod that listens for updates from theClusterService. -
PlannerSettings
public PlannerSettings(DataPartitioning defaultDataPartitioning, ByteSizeValue valuesLoadingJumboSize, int luceneTopNLimit, ByteSizeValue intermediateLocalRelationMaxSize) Ctor for testing.
-
-
Method Details
-
defaultDataPartitioning
-
valuesLoadingJumboSize
-
luceneTopNLimit
public int luceneTopNLimit()MaximumLIMITthat 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_numberdocs and then materializes only the lastpage_sizedocuments. Traditionally, Elasticsearch limits thatpage_size * page_numberwhich it calls the"result window". So! ESQL defaults to the same default -10,000. -
intermediateLocalRelationMaxSize
-