Github user shashank734 commented on the issue:
https://github.com/apache/flink/pull/4943
I think this is due to this issue :
https://issues.apache.org/jira/browse/FLINK-9202
---
Github user shashank734 commented on the issue:
https://github.com/apache/flink/pull/4943
@zentol Thanks, I think it's the wrong place to ask But Actually We have
tried to use AvroTypeInfo, But it was unable to restore from the savepoint
(Note we have changed the schema and class
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4943
@shashank734 The commits are contained in 1.4 already. Have you read
[this](https://github.com/apache/flink/pull/4943#issuecomment-342156083)
comment?
---
Github user shashank734 commented on the issue:
https://github.com/apache/flink/pull/4943
@StephanEwen Are these changes part of 1.5 or 1.4, Do you have any example
how I can use this with states and CEP? Please give me some hint. I have seen
test cases of Input and Output only.
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4943
ð
Btw, now users have to manually depend on `flink-avro` in their projects
where before they didn't necessarily have to, right? If yes, we should also put
it in the release notes.
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4943
I would suggest adding that last paragraph in the `release notes` field of
FLINK-6022 so we don't forget about this.
---
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/4943
I updated this PR with the following proposed solution:
1. Avro is always part of the user code space, and hence will be loaded
into the user code classloader. This solves multiple
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/4943
Thanks for the review, addressing the comments.
I found the problem with the backwards compatibility: It is the Avro
version upgrade.
Avro types generated with Avro 1.7.7 (Flink 1.3)
