Hi,
I think this is a good idea!
Some PRs (mostly by dependabot) are not merged because Avro needs to be JDK
8 compatible and the dependencies require a newer JDK...
I am not sure whether Avro 1.12.0 still needs to be JDK 8 compatible or not.
Martin
On Sat, Jan 6, 2024 at 5:55 PM Chad Preisler
The spec states that the media type for Avro should be "avro/binary, which is
in conflict with the common pattern of the IANA media type registry and Avro is
also not registered there.
In the CNCF CloudEvents and CNCF xRegistry efforts we take Avro dependencies
and we also take dependencies on
More and more libraries these days are dropping support for JDK 8 (at least
Spring Boot 3, Jakarta EE 11, Mockito 5, among others), so I personally
think it would be fine to drop support for JDK 8 in 1.12.0, or maybe even
bump the Avro release to 2.0.0 with the removal of JDK 8 support?
On Mon, Ja
dependabot[bot] opened a new pull request, #2678:
URL: https://github.com/apache/avro/pull/2678
Bumps [proc-macro2](https://github.com/dtolnay/proc-macro2) from 1.0.75 to
1.0.76.
Release notes
Sourced from https://github.com/dtolnay/proc-macro2/releases";>proc-macro2's
releases.
dependabot[bot] opened a new pull request, #2679:
URL: https://github.com/apache/avro/pull/2679
Bumps [serial_test](https://github.com/palfrey/serial_test) from 2.0.0 to
3.0.0.
Release notes
Sourced from https://github.com/palfrey/serial_test/releases";>serial_test's
releases.
dependabot[bot] opened a new pull request, #2680:
URL: https://github.com/apache/avro/pull/2680
Bumps [serde](https://github.com/serde-rs/serde) from 1.0.194 to 1.0.195.
Release notes
Sourced from https://github.com/serde-rs/serde/releases";>serde's releases.
v1.0.195
+1 to move to Java 11. Most of our downstream projects have moved out of
Java 8 and the fact that we are getting behind on our own dependencies is a
sign of the current state of the ecosystem. So good to move, and no need to
change the full version. 1.12.0 should be good.
We should probably tackle
I lack the background on why that odd "avro/binary" style was chosen.
Registering an IANA media type for Avro and supporting it in the different
implementations sounds like an excellent idea!
Other Apache projects have registered IANA types like
'application/vnd.apache.thrift.binary' or
'applicati
This sounds like an issue just waiting for someone to be sufficiently irked!
Is there any reason NOT to use the common pattern? I really haven't run
across any use cases that use the media type at all!
All my best, Ryan
On Mon, Jan 8, 2024 at 6:58 PM Ismaël Mejía wrote:
> I lack the backgroun
I can do both depending on the timeline for 1.12.0. If you are cutting a
release this week, that probably won't work. I don't think it will take
long to switch to JDK 11 as your default, but I'm not familiar with testing
changes to the github actions. Basically there will be some learning curve
for
zejiong dong created AVRO-3927:
--
Summary: [Rust] support custom attributes in list and map
Key: AVRO-3927
URL: https://issues.apache.org/jira/browse/AVRO-3927
Project: Apache Avro
Issue Type: I
ZENOTME opened a new pull request, #2681:
URL: https://github.com/apache/avro/pull/2681
## What is the purpose of the change
*(For example: This pull request improves file read performance by buffering
data, fixing AVRO-.)*
## Verifying this change
*(Plea
12 matches
Mail list logo
