milleruntime commented on issue #2776: URL: https://github.com/apache/accumulo/issues/2776#issuecomment-1156332245
> This is just a warning... what's the real-world impact? Are these effectively not serializable? Like, if we try, they could never have been serialized? I wrote a basic write/read test for an `Authorizations` object and was able to serialize it. See https://github.com/apache/accumulo/pull/2777#issuecomment-1155517364. I could add one test for all the classes to see if we are able to serialize them all. > If they are still serializable as a whole, but behaves in a weird way due to the fields not being serializable, then we may need to try to preserve existing weird behavior or try to change behavior through a deprecation cycle. It seems that these objects could throw an exception in newer versions of [Java](https://docs.oracle.com/en/java/javase/17/docs/specs/serialization/output.html). I found this openJDK issue with the following comment: "If the serialization mechanism attempts to serialize an object that is not serializable at runtime a NotSerializableException can result." https://bugs.openjdk.org/browse/JDK-8274336 -- 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]
