Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/386#issuecomment-74080897
Merged to release-0.8 in:
http://git-wip-us.apache.org/repos/asf/flink/commit/10f89c73
---
If your project is set up for it, you can reply to this email and have your
re
Github user rmetzger closed the pull request at:
https://github.com/apache/flink/pull/386
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/386#issuecomment-74068908
Ah no. Its not a good idea ;)
We don't see that the user is using an Avro POJO when we use the POJO
serializer.
So we have to register the types always.
---
If y
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/386#issuecomment-74068411
I like the idea. Can we make the registration conditional on whether the
enclosing type is an Avro Type?
---
If your project is set up for it, you can reply to this e
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/386#issuecomment-74068511
Yep.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/386
[FLINK-1391] Register common Avro types at Kryo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rmetzger/flink kryo081-2
Alternatively you can