- 10 5月, 2017 6 次提交
-
-
由 twalthr 提交于
This closes #3619.
-
由 twalthr 提交于
This closes #3318
-
由 rtudoran 提交于
This closes #3849.
-
由 Hequn Cheng 提交于
This closes #3850.
-
由 godfreyhe 提交于
This closes #3815.
-
由 sunjincheng121 提交于
This closes #3841.
-
- 09 5月, 2017 3 次提交
-
-
由 David Anderson 提交于
This closes #3823
-
由 David Anderson 提交于
This closes #3821
-
由 Stefan Richter 提交于
-
- 08 5月, 2017 8 次提交
-
-
由 Kurt Young 提交于
This closes #3803.
-
由 Robert Metzger 提交于
-
由 tedyu 提交于
-
由 Stefan Richter 提交于
[FLINK-6475] [checkpoint] Incremental snapshots in RocksDB should not hold lock during async file upload
-
由 Stefan Richter 提交于
[FLINK-6471] [checkpoint] Fix RocksDBStateBackendTest#testCancelRunningSnapshot failing sporadically
-
由 Tzu-Li (Gordon) Tai 提交于
Previously, the CompatibilityResult class accepts a full-blown TypeSerializer for its convert deserializer, which will actually only ever be used for deserialization. This commit narrows down the interface by introducing a new TypeDeserializer interface that contains only the read methods. This closes #3834. This closes #3804.
-
由 Tzu-Li (Gordon) Tai 提交于
This commit adds the functionality of allowing serializer upgrades for Flink's managed state. It consists of 2 major changes: 1) new user-facing API in `TypeSerializer`, and 2) activate serializer upgrades in state backends. For 1) new user-facing API for `TypeSerializer`, the following is added: - new class: TypeSerializerConfigSnapshot - new class: CompatibilityResult - new method: TypeSerializer#snapshotConfiguration() - new method: TypeSerializer#ensureCompatibility(TypeSerializerConfigSnapshot) Generally speaking, configuration snapshots contains a point-in-time view of a serializer's state / configuration, and is persisted along with checkpoints. On restore, the configuration is confronted with the new serializer of the state to check for compatibility, which may introduce reconfiguration of the new serializer to be compatible. This compatibility check is integrated in the state backends' restore flow in 2). Currently, if the check results in the need to perform state migration, the restore simply fails as the state migration feature isn't yet available.
-
由 Tzu-Li (Gordon) Tai 提交于
Previously, the TypeSerializerSerializationProxy only uses the dummy ClassNotFoundDummyTypeSerializer as a placeholder in the case where the user uses a completely new serializer and deletes the old one. There is also the case where the user changes the original serializer's implementation and results in an InvalidClassException when trying to deserialize the serializer. We should also use the ClassNotFoundDummyTypeSerializer as a temporary placeholder in this case.
-
- 07 5月, 2017 16 次提交
-
-
由 Shuyi Chen 提交于
This closes #3793.
-
由 sunjincheng121 提交于
This closes #3697.
-
由 Tzu-Li (Gordon) Tai 提交于
This commit adds some general improvements to the rescalable implementation of FlinkKinesisConsumer, including: - Refactor setup procedures in KinesisDataFetcher so that duplicate work isn't done on a restored run - Strengthen corner cases where fetcher was not fully seeded with initial state when snapshot is taken This closes #3001.
-
由 Tony Wei 提交于
-
由 Stephan Ewen 提交于
-
由 shuai.xus 提交于
-
由 Stephan Ewen 提交于
This method exploits the fact that verties are already in topological order. This closes #3773
-
由 shuai.xus 提交于
-
由 shuai.xus 提交于
[FLINK-5867] [flip-1] Support restarting only pipelined sub-regions of the ExecutionGraph on task failure
-
由 David Anderson 提交于
This closes #3822
-
由 David Anderson 提交于
This closes #3828
-
由 Stephan Ewen 提交于
-
由 Stephan Ewen 提交于
This preserves old config keys as deprecated keys where the key was already present in an earlier release. This also re-arranges config options to form logical sections in the file and harmonized JavaDoc formatting style.
-
由 Stephan Ewen 提交于
-
由 Stephan Ewen 提交于
'lshift(...)' is not defined by default in some commonly used awk versions.
-
由 Nico Kruber 提交于
Instead, allow the configuration with the following three new (more flexible) parameters: * "taskmanager.network.memory.fraction": fraction of JVM memory to use for network buffers (default: 0.1) * "taskmanager.network.memory.min": minimum memory size for network buffers (default: 64 MB) * "taskmanager.network.memory.max": maximum memory size for network buffers (default: 1 GB) This closes #3721
-
- 06 5月, 2017 7 次提交
-
-
由 Nico Kruber 提交于
-
由 Nico Kruber 提交于
-
由 Stephan Ewen 提交于
-
由 Stephan Ewen 提交于
-
由 Fabian Hueske 提交于
-
由 Hequn Cheng 提交于
-
由 Hequn Cheng 提交于
-