-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(agama): use a mixed strategy for serialization #6834
Labels
Milestone
Comments
mo-auto
added
comp-agama
Touching folder /agama
kind-feature
Issue or PR is a new feature request
labels
Nov 29, 2023
jgomer2001
added a commit
that referenced
this issue
Dec 1, 2023
jgomer2001
added a commit
that referenced
this issue
Dec 1, 2023
jgomer2001
added a commit
that referenced
this issue
Dec 1, 2023
jgomer2001
added a commit
that referenced
this issue
Dec 1, 2023
5 tasks
yuriyz
pushed a commit
that referenced
this issue
Dec 1, 2023
devrimyatar
pushed a commit
that referenced
this issue
Dec 7, 2023
* chore: misc enhancements #6834 * feat: implement a mixed strategy for serialization of state #6834 * feat: update configuration for #6834 * docs: update docs in accordance to new serialization behavior #6834 Signed-off-by: Mustafa Baser <[email protected]>
devrimyatar
pushed a commit
that referenced
this issue
Dec 30, 2023
* chore: misc enhancements #6834 * feat: implement a mixed strategy for serialization of state #6834 * feat: update configuration for #6834 * docs: update docs in accordance to new serialization behavior #6834 Signed-off-by: Mustafa Baser <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
There is not a definite fix for issue #6528
A way to mitigate the problem is using a combination of Java and kryo serialization based on some heuristics, for instance:
a) Exceptions should be serialized with Java. kryo should not be used here according to my personal experience. Also this comment
b) Objects belonging to packages
java.*
,sun.*
,com.sun.*
,jdk.*
should be serialized with Javac) use kryo in other cases
Behaviors in b and c should be parameterized. As such, we can replace property
serializerType
in the agama configuration with the specific policiesIn all cases, when serialization of a Java object is about to occur, we have to log the class and the type of serializer attempted - this helps troubleshooting in case the process fails
This overhaul requires some amount of doc updates too
The text was updated successfully, but these errors were encountered: