Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".
Discussion thread | Vote thread | here (<- link to
---|---|
https://lists.apache.org | |
/thread/m67s4qfrh660lktpq7yqf9docvvf5o9l | |
Vote thread | https://lists.apache.org |
/thread/2xmcxs67xxzwool554fglrnklyvw348h | |
JIRA | |
Release | <Flink Version> |
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
The following methods in ExecutionConfig
will be deprecated
and be removed in flink-2.0
Method | Annotation |
org.apache.flink.api.common.ExecutionConfig#registerKryoType(Class<?> type) | @Public |
org.apache.flink.api.common.ExecutionConfig#registerPojoType(Class<?> type) | |
org.apache.flink.api.common.ExecutionConfig#registerTypeWithKryoSerializer(Class<?> type, Class<? extends Serializer> serializerClass) | |
org.apache.flink.api.common.ExecutionConfig#registerTypeWithKryoSerializer(Class<?> type, T serializer) | |
org.apache.flink.api.common.ExecutionConfig#addDefaultKryoSerializer(Class<?> type, Class<? extends Serializer<?>> serializerClass) | |
org.apache.flink.api.common.ExecutionConfig#addDefaultKryoSerializer( Class<?> type, T serializer) | |
org.apache.flink.api.common.ExecutionConfig#getRegisteredKryoTypes() | |
org.apache.flink.api.common.ExecutionConfig#getRegisteredPojoTypes() | |
org.apache.flink.api.common.ExecutionConfig#getRegisteredTypesWithKryoSerializerClasses() | |
org.apache.flink.api.common.ExecutionConfig#getRegisteredTypesWithKryoSerializers() | |
org.apache.flink.api.common.ExecutionConfig#getDefaultKryoSerializerClasses() | |
org.apache.flink.api.common.ExecutionConfig#getDefaultKryoSerializers() | |
org.apache.flink.api.common.ExecutionConfig#enableForceAvro() | |
org.apache.flink.api.common.ExecutionConfig#enableForceKryo() | |
org.apache.flink.api.common.ExecutionConfig#enableGenericTypes() | |
org.apache.flink.api.common.ExecutionConfig#setForceAvro(boolean forceAvro) | |
org.apache.flink.api.common.ExecutionConfig#setForceKryo(boolean forceKryo) | |
org.apache.flink.api.common.ExecutionConfig#disableForceAvro() | |
org.apache.flink.api.common.ExecutionConfig#disableForceKryo() | |
org.apache.flink.api.common.ExecutionConfig#disableGenericTypes() | |
org.apache.flink.api.common.ExecutionConfig#hasGenericTypesDisabled() | |
org.apache.flink.api.common.ExecutionConfig#isForceAvroEnabled() | |
org.apache.flink.api.common.ExecutionConfig#isForceKryoEnabled() |
The following methods in StreamExecutionEnvironment
will be deprecated and removed in flink-2.0
Method | Annotation |
org.apache.flink.streaming.api.environment.StreamExecutionEnvironment#registerType(Class<?> type) | @Public |
org.apache.flink.streaming.api.environment.StreamExecutionEnvironment#registerTypeWithKryoSerializer(Class<?> type, Class<? extends Serializer> serializerClass) | |
org.apache.flink.streaming.api.environment.StreamExecutionEnvironment#registerTypeWithKryoSerializer(Class<?> type, T serializer) | |
org.apache.flink.streaming.api.environment.StreamExecutionEnvironment#addDefaultKryoSerializer(Class<?> type, Class<? extends Serializer<?>> serializerClass) | |
org.apache.flink.streaming.api.environment.StreamExecutionEnvironment#addDefaultKryoSerializer(Class<?> type, T serializer) |
The following method in TypeInformation
will be deprecated and removed in flink-2.0
Method | Annotation |
org.apache.flink.api.common.typeinfo#createSerializer(ExecutionConfig config) | @PublicEvolving |
Users can configure pipeline.force-avro
, pipeline.force-kryo
and pipeline.generic-types
in job after enableForceAvro
, enableForceKryo
and enableGenericTypes
are deprecated and removed as follows.
...
The relevant method in TypeInformation
Method | Annotation |
org.apache.flink.api.common.typeinfo#createSerializer(SerializerConfig config) | @PublicEvolving |
Disable Kryo By Default
Currently, option pipeline.generic-types
in Flink is used to enable/disable Kryo
serialzier, its default value is true
which means Flink will use Kryo
as fallback serializer. This causes Kryo to be used by default to serialize some user-defined data without the user being aware of it, which can lead to incompatibility between the new and old versions of the job state during version upgrades. To avoid this issue, in Flink-2.0
, the default value of pipeline.generic-types
can be changed to false
to prevent the usage of the Kryo serializer without the user's knowledge.
...