配置
- Overview
- Execution Options
- Optimizer Options

配置

By default, the Table & SQL API is preconfigured for producing accurate results with acceptableperformance.

Depending on the requirements of a table program, it might be necessary to adjustcertain parameters for optimization. For example, unbounded streaming programs may need to ensurethat the required state size is capped (see streaming concepts).

Overview
Execution Options
Optimizer Options

Overview

In every table environment, the TableConfig offers options for configuring the current session.

For common or important configuration options, the TableConfig provides getters and setters methodswith detailed inline documentation.

For more advanced configuration, users can directly access the underlying key-value map. The followingsections list all available options that can be used to adjust Flink Table & SQL API programs.

Attention Because options are read at different point in timewhen performing operations, it is recommended to set configuration options early after instantiating atable environment.

// instantiate table environment
TableEnvironment tEnv = ...
// access flink configuration
Configuration configuration = tEnv.getConfig().getConfiguration();
// set low-level key-value options
configuration.setString("table.exec.mini-batch.enabled", "true");
configuration.setString("table.exec.mini-batch.allow-latency", "5 s");
configuration.setString("table.exec.mini-batch.size", "5000");

// instantiate table environment
val tEnv: TableEnvironment = ...
// access flink configuration
val configuration = tEnv.getConfig().getConfiguration()
// set low-level key-value options
configuration.setString("table.exec.mini-batch.enabled", "true")
configuration.setString("table.exec.mini-batch.allow-latency", "5 s")
configuration.setString("table.exec.mini-batch.size", "5000")

# instantiate table environment
t_env = ...
# access flink configuration
configuration = t_env.get_config().get_configuration();
# set low-level key-value options
configuration.set_string("table.exec.mini-batch.enabled", "true");
configuration.set_string("table.exec.mini-batch.allow-latency", "5 s");
configuration.set_string("table.exec.mini-batch.size", "5000");

Attention Currently, key-value options are only supportedfor the Blink planner.

Execution Options

The following options can be used to tune the performance of the query execution.

Key	Default	Description
##### table.exec.async-lookup.buffer-capacityBatchStreaming	100	The max number of async i/o operation that the async lookup join can trigger.
##### table.exec.async-lookup.timeoutBatchStreaming	"3 min"	The async timeout for the asynchronous operation to complete.
##### table.exec.disabled-operatorsBatch	(none)	Mainly for testing. A comma-separated list of operator names, each name represents a kind of disabled operator.Operators that can be disabled include "NestedLoopJoin", "ShuffleHashJoin", "BroadcastHashJoin", "SortMergeJoin", "HashAgg", "SortAgg".By default no operator is disabled.
##### table.exec.mini-batch.allow-latencyStreaming	"-1 ms"	The maximum latency can be used for MiniBatch to buffer input records. MiniBatch is an optimization to buffer input records to reduce state access. MiniBatch is triggered with the allowed latency interval and when the maximum number of buffered records reached. NOTE: If table.exec.mini-batch.enabled is set true, its value must be greater than zero.
##### table.exec.mini-batch.enabledStreaming	false	Specifies whether to enable MiniBatch optimization. MiniBatch is an optimization to buffer input records to reduce state access. This is disabled by default. To enable this, users should set this config to true. NOTE: If mini-batch is enabled, 'table.exec.mini-batch.allow-latency' and 'table.exec.mini-batch.size' must be set.
##### table.exec.mini-batch.sizeStreaming	-1	The maximum number of input records can be buffered for MiniBatch. MiniBatch is an optimization to buffer input records to reduce state access. MiniBatch is triggered with the allowed latency interval and when the maximum number of buffered records reached. NOTE: MiniBatch only works for non-windowed aggregations currently. If table.exec.mini-batch.enabled is set true, its value must be positive.
##### table.exec.resource.default-parallelismBatchStreaming	-1	Sets default parallelism for all operators (such as aggregate, join, filter) to run with parallel instances. This config has a higher priority than parallelism of StreamExecutionEnvironment (actually, this config overrides the parallelism of StreamExecutionEnvironment). A value of -1 indicates that no default parallelism is set, then it will fallback to use the parallelism of StreamExecutionEnvironment.
##### table.exec.resource.external-buffer-memoryBatch	"10 mb"	Sets the external buffer memory size that is used in sort merge join and nested join and over window.
##### table.exec.resource.hash-agg.memoryBatch	"128 mb"	Sets the managed memory size of hash aggregate operator.
##### table.exec.resource.hash-join.memoryBatch	"128 mb"	Sets the managed memory for hash join operator. It defines the lower limit.
##### table.exec.resource.sort.memoryBatch	"128 mb"	Sets the managed buffer memory size for sort operator.
##### table.exec.shuffle-modeBatch	"batch"	Sets exec shuffle mode. Only batch or pipeline can be set.batch: the job will run stage by stage. pipeline: the job will run in streaming mode, but it may cause resource deadlock that receiver waits for resource to start when the sender holds resource to wait to send data to the receiver.
##### table.exec.sort.async-merge-enabledBatch	true	Whether to asynchronously merge sorted spill files.
##### table.exec.sort.default-limitBatch	-1	Default limit when user don't set a limit after order by. -1 indicates that this configuration is ignored.
##### table.exec.sort.max-num-file-handlesBatch	128	The maximal fan-in for external merge sort. It limits the number of file handles per operator. If it is too small, may cause intermediate merging. But if it is too large, it will cause too many files opened at the same time, consume memory and lead to random reading.
##### table.exec.source.idle-timeoutStreaming	"-1 ms"	When a source do not receive any elements for the timeout time, it will be marked as temporarily idle. This allows downstream tasks to advance their watermarks without the need to wait for watermarks from this source while it is idle.
##### table.exec.spill-compression.block-sizeBatch	"64 kb"	The memory size used to do compress when spilling data. The larger the memory, the higher the compression ratio, but more memory resource will be consumed by the job.
##### table.exec.spill-compression.enabledBatch	true	Whether to compress spilled data. Currently we only support compress spilled data for sort and hash-agg and hash-join operators.
##### table.exec.window-agg.buffer-size-limitBatch	100000	Sets the window elements buffer size limit used in group window agg operator.

Optimizer Options

The following options can be used to adjust the behavior of the query optimizer to get a better execution plan.

Key	Default	Description
##### table.optimizer.agg-phase-strategyBatchStreaming	"AUTO"	Strategy for aggregate phase. Only AUTO, TWO_PHASE or ONE_PHASE can be set.AUTO: No special enforcer for aggregate stage. Whether to choose two stage aggregate or one stage aggregate depends on cost. TWO_PHASE: Enforce to use two stage aggregate which has localAggregate and globalAggregate. Note that if aggregate call does not support optimize into two phase, we will still use one stage aggregate.ONE_PHASE: Enforce to use one stage aggregate which only has CompleteGlobalAggregate.
##### table.optimizer.distinct-agg.split.bucket-numStreaming	1024	Configure the number of buckets when splitting distinct aggregation. The number is used in the first level aggregation to calculate a bucket key 'hash_code(distinct_key) % BUCKET_NUM' which is used as an additional group key after splitting.
##### table.optimizer.distinct-agg.split.enabledStreaming	false	Tells the optimizer whether to split distinct aggregation (e.g. COUNT(DISTINCT col), SUM(DISTINCT col)) into two level. The first aggregation is shuffled by an additional key which is calculated using the hashcode of distinct_key and number of buckets. This optimization is very useful when there is data skew in distinct aggregation and gives the ability to scale-up the job. Default is false.
##### table.optimizer.join-reorder-enabledBatchStreaming	false	Enables join reorder in optimizer. Default is disabled.
##### table.optimizer.join.broadcast-thresholdBatch	1048576	Configures the maximum size in bytes for a table that will be broadcast to all worker nodes when performing a join. By setting this value to -1 to disable broadcasting.
##### table.optimizer.reuse-source-enabledBatchStreaming	true	When it is true, the optimizer will try to find out duplicated table sources and reuse them. This works only when table.optimizer.reuse-sub-plan-enabled is true.
##### table.optimizer.reuse-sub-plan-enabledBatchStreaming	true	When it is true, the optimizer will try to find out duplicated sub-plans and reuse them.
##### table.optimizer.source.predicate-pushdown-enabledBatchStreaming	true	When it is true, the optimizer will push down predicates into the FilterableTableSource. Default value is true.