Hi everyone,
Below is one opinion of the subject.
The most robust way to determine if two schemata are the same is how they
serialise datums to bytes. Schema evolution allows us to match schemata if
they are not the same, but similar enough.
Default values, both for fields and enums, are perfect
Renar Narubin created AVRO-3821:
---
Summary: Rust: Record (de?)serialization is sensitive to order of
fields in struct
Key: AVRO-3821
URL: https://issues.apache.org/jira/browse/AVRO-3821
Project: Apache A
Kousuke Saruta created AVRO-3820:
Summary: Don't allow invalid field names
Key: AVRO-3820
URL: https://issues.apache.org/jira/browse/AVRO-3820
Project: Apache Avro
Issue Type: Bug
C
On Wed, Aug 2, 2023 at 10:14 AM Oscar Westra van Holthe - Kind <
os...@westravanholthe.nl> wrote:
> Hi everyone,
>
> The proposal so task has much to offer that (at least in my opinion) is
> worth the extra effort of maintaining a third branch.
>
> I'm not certain if we should also add non-breakin
Hi,
On Tue, Aug 1, 2023 at 9:13 PM Ryan Skraba wrote:
> Bringing this subject back while it's still a bit fresh :D
>
> For the moment we seem to agree... But does anybody have any
> objections _against_ maintaining two major version (by keeping the
> *three* branches ready to release)?
>
I beli
Hi everyone,
The proposal so task has much to offer that (at least in my opinion) is
worth the extra effort of maintaining a third branch.
I'm not certain if we should also add non-breaking changes to the last
maintenance release. Does this mean we release each branch separately when
ready, and n
