weiqingy commented on PR #26903: URL: https://github.com/apache/flink/pull/26903#issuecomment-3201632814
> @weiqingy this is a nice addition. I wondered can we say what state is not compatible between v1 and v2. I suspect it should work apart from serializing state that involves: > > * some / all custom serializers > * Scala Case Class datatype > * POJOs using Kryo > * General Class Types using Kryo > > Anything else we should add to the list? If this is the case it would really useful to document these restrictions to help Flink users know if there are likely to hit migration issues or not. Thanks for reviewing! I agree it’s valuable to document which cases are not guaranteed to be compatible. Since I don’t have a complete list yet, my suggestion is to keep this PR minimal and follow up with a dedicated update that expands on those scenarios. How does that sound? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
