Page History

Configuration

Comment

Suggested key

Type of the field

Exists in 1.9 

autoTypeRegistration

exec.auto-type-registration

boolean

autoWatermarkInterval

We could use Duration for ConfigOption

exec.auto-watermark-interval

long

closureCleaner

exec.closure-cleaner-level

ClosureCleanerLevel

defaultInputDependencyConstraint

exec.input-dependency-constraint

Enum<SuffleMode>

table.exec.shuffle-mode

(ExecutionConfigOptions) - drop this optionEnum<InputDependencyConstraint>

defaultKryoSerializerClasses

We should support only this version as it takes Class<? extends Serializer<?>>. This simplifies the serialization.

exec.default-kryo-serializers

Map<Class, Class<Serializer<?>>>

defaultKryoSerializers

We do not want to support this option as it stores SerializableSerializer. We see no point in configuring the serializers from Java-serialized strings in Base64 encoding.

not supported

Map<Class, SerializableSerializer<?>>

disableGenericTypes

we should invert the logic in the ConfigOption. true means enabled, false disabled

exec.generic-types

boolean

enableAutoGeneratedUIDs

exec.auto-generated-uids

boolean

executionMode

exec.mode

Enum<ExecutionMode>

executionRetryDelay/

numberOfExecutionRetries

Deprecated

not supported

long/int

forceAvro

exec.force-avro

boolean

forceKryo

exec.force-kryo

boolean

setGlobalJobParameters

exec.global-job-parameters

Map<String, String>

latencyTrackingInterval

reuse the existing

long

metrics.latency.interval(MetricOptions)

setMaxParallelism

exec.max-parallelism

int

objectReuse

exec.object-reuse

boolean

setParallelism

reuse the existing

int

parallelism.default(CoreOptions)

table.exec.resource.default-parallelism (ExecutionConfigOptions) - drop this Table specific option

printProgressDuringExecution

exec.sysout-logging

boolean

registeredKryoTypes

exec.registered-kryo-types

List<Class<?>>

registeredPojoTypes

exec.registered-pojo-types

List<Class<?>>

registeredTypesWithKryoSerializers

We do not want to support this option as it stores SerializableSerializer. We see no point in configuring the serializers from MD5 encoding.

not supported

Map<Class, Serializer<?>>

registeredTypesWithKryoSerializerClasses

We should support only this version as it takes Class<? extends Serializer<?>>. This simplifies the serialization.

not supported

Map<Class, Class<Serializer<?>>>

setRestartStrategy

On the client side we need to convert the option to RestartStrategyConfiguration. It does not support custom restart strategy. We would also flatten the configuration structure.

exec.restart-strategy

RestartStrategy

restart-strategy(ConfigConstants) (not a proper ConfigOption yet)

taskCancellationIntervalMillis

reuse the existing

long

task.cancellation.interval (TaskManagerOptions)

taskCancellationTimeoutMillis

reuse the existing

long

task.cancellation.timeout (TaskManagerOptions)

useSnapshotCompression

exec.snapshot-compression

boolean

codeAnalysisMode

Deprecated, has no effect

not supported

---

failTaskOnCheckpoint

Deprecated

not supported

boolean