{"push_id":1111298629,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"96b353d98f6b6d441ebedf69ec12cfa333a1d7c9","before":"099fdfa0c5789f509242f83e8f808d552e63ee8d","commits":[{"sha":"48b469ad4f0da466b347071cea82913965645de3","author":{"email":"180f55e8350155df1048ad760eeaa1cff137f014@apache.org","name":"Maximilian Michels"},"message":"[FLINK-3701] enable reuse of ExecutionConfig\n\nDepending on the context, the ExecutionConfig's type fields may either\nbe deserialized using a custom class loader or the default class\nloader. It may be explicitly serialized for the Task or shipped inside\nthe PojoSerializer where it is serialized or directly passed in local\nmode. An ExecutionConfig may be reused and thus its fields can't be set\nto null after it has been shipped once.\n\nThe entire ExecutionConfig is now serialized upon setting it on the\nJobGraph. It is not passed through the JobGraph's constructor but set\nexplicitly on the JobGraph. If no ExecutionConfig has been set, the\ndefault is used. Unlike before, no code may modify the ExecutionConfig\nafter it has been set on the JobGraph.\n\nThis closes #1913","distinct":true,"url":"https://api.github.com/repos/ueshin/apache-flink/commits/48b469ad4f0da466b347071cea82913965645de3"},{"sha":"96b353d98f6b6d441ebedf69ec12cfa333a1d7c9","author":{"email":"180f55e8350155df1048ad760eeaa1cff137f014@apache.org","name":"Maximilian Michels"},"message":"[FLINK-3856] adapt test assertion to type stack changes\n\nAddition to bbd02d24bc7547e2c9384d713b20f86682cac08c.\n\nThe java.lang.Date type shouldn't be an automatically Kryo registered\nanymore.","distinct":true,"url":"https://api.github.com/repos/ueshin/apache-flink/commits/96b353d98f6b6d441ebedf69ec12cfa333a1d7c9"}]}