[site] Announce Avro release - #3945
Conversation
ad9fad9 to
d270720
Compare
joebowbeer
left a comment
There was a problem hiding this comment.
Suggested workaround is deprecated?
| ## Breaking Changes | ||
|
|
||
| ### Java | ||
| * [AVRO-4189](https://issues.apache.org/jira/browse/AVRO-4189) ([#3693](https://github.com/apache/avro/pull/3693)): Classes referenced by the `java-class` schema property are now validated when using the fast reader. Avro will throw a `SecurityException` instead of instantiating non-permitted classes. Set the system property `org.apache.avro.SERIALIZABLE_PACKAGES` to `*`, or call `ClassSecurityValidator.setGlobal(...)`, to restore the old behavior. |
There was a problem hiding this comment.
Hello, thanks for the comment -- I'm also confused about the SERIALIZABLE_PACKAGES being deprecated, or where the "as discussed" occurred, although I have to admit that I wasn't active in the mailing lists at that time. The system property is still present and being used, and isn't marked as deprecated in 1.12.2 or 1.13.0-SNAPSHOT.
I'd like to rewrite this section to give a better explanation.
There was a problem hiding this comment.
Thanks for clarifying!
It is the static fields of SpecificDatumReader (both) that are deprecated, not the system properties.
There was a problem hiding this comment.
I'm definitely going to put some comments in the code and we NEED to have this documented somewhere on the website! I've created https://issues.apache.org/jira/browse/AVRO-4335 as a placeholder.
|
I've rewritten this Breaking Changes section, is it clearer to follow? |
Yes. Thanks! It is the static fields of SpecificDatumReader (both) that are deprecated, not the system properties. |
What is the purpose of the change
Announce the Avro 1.12.2 release on the website blog
Verifying this change
This change is a documentation change without any test coverage.
Documentation