expediagroup / avro-compatibility Goto Github PK

http://avro.apache.org/releases.html#2+September+2019%3A+Avro+1.9.1+Released

Hi.

We would like to use this project in our workflow at Hapag Llyod.
As we are required to make sure that all dependencies are up to date to reduce security risks, we sadly can't use the project in it's current state.

I've seen that you are using dependabot to automatically update dependencies in some of your other open source projects.
You also seem to have some projects with Github Workflows allowing changes to be automatically published to maven.

Would you be able to include those tools in this repository as well, so that the dependencies will easily be kept up to date without much effort for you?

We would really appreciate it.
Thanks a lot
Julius

PS: If you want, we can also try to make the changes and create a PR for them, so that you will only need to add the required variables to the project.

Given the following schemas

{
	"type": "record",
	"name": "Example",
	"namespace": "example.1.0",
	"fields": [{
		"name": "name",
		"type": "string"
	}]
}

{
	"type": "record",
	"name": "Example",
	"namespace": "example.2.0",
	"fields": [{
		"name": "name",
		"type": "string"
	}, {
		"name": "age",
		"type": "int",
		"default": 0
	}]
}

The following all return false

Compatibility.checkThat(one).canBeReadBy(two).isCompatible();
Compatibility.checkThat(two).canBeReadBy(one).isCompatible();
Compatibility.checkThat(one).canRead(two).isCompatible();
Compatibility.checkThat(two).canRead(one).isCompatible();

But reading works

The following data written with example.1.0.Example...

{"name": "foo"}

...when read with example.2.0.Example becomes...

{"name": "foo", "age": 0}

My actual question

While I see the sense for this library to rely on org.apache.avro.SchemaCompatibility I'm wondering how to view/reason around scenarios such as the one described here with two clearly(?) compatible schemas that "all" compatibility logic claim are not compatible.

(perhaps this is a question better asked to the Avro users mailing list?)

In the CompatibilityTest schemaString8 contains invalid json