[GitHub] [accumulo] ctubbsii commented on issue #2776: Warnings: non-transient instance field of a serializable class declared with a non-serializable type

[GitBox <gi...@apache.org>]

ctubbsii commented on issue #2776:
URL: https://github.com/apache/accumulo/issues/2776#issuecomment-1155926593

   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? If they have never been serializable, then we're not breaking any user code by dropping it... we're just breaking binary compatibility, which we don't guarantee across minor/major versions anyway, and we can just drop the useless interface in 3.0.
   
   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.


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org