there where some api/converter/encoding changes and fixes, we should use: holixon/avro-registry-adapter#44

https://search.maven.org/artifact/io.holixon.avro/avro-registry-adapter-bom/0.0.3/jar

Instead of manual creation, let github create release notes (as drafts).

@jangalinski please move this to holixon

Not as nice ... fails when I actually serialize/deserialize

I added a disabled test to the AvroMetaDataExtTest that fails when serializing LocalDate.
This is non trivial ... I would like to close this issue, so we at least have metadata support and then work on the metadata/bytes via a separate issue. thoughts?

Originally posted by @jangalinski in #108 (comment)

currently, we use the holixon/axon-framework-bom, but meanwhile the official axon bom seems to be up to date and stable, so let's us it

• upcaster by schema (defaults)
• custom specific upcaster based on generic record
• generic upcasting based on avro incompatibilities

we have to use Optional.ofNullable instead of "of"

It is encoded in the SingleObject Byte array. But it can't hurt to include it as metadata ... easier to access and check.

Provide initial version of docs

Currently, the metadata of a message is serialized via Jackson ... this should be avro as well

to prove that serialization of events (and metadata) works correctly, set up a "real" itest based on the axon server docker image using testcontainers.

The Axon Server OSGi plugin provides an SPI for Registry Plugins to provide a JSON converter using a particular registry. The Apicurio registry plugin should implement this SPI and deliver configuration for connection with an Apicurio registry and provide such a JSON converter.

We need a nice docs site for this project.

In order to use the Axon Server console, which allows to search for events, a non-binary representation as simple JSON is required. The server OSGi plugin should deliver this functionality.

Hello,

In brief, All events are defined as Avro Versioned Schemas, and the Java Classes are Autogenerated (perfectly). Multiple axon-based spring boot applications consume these events. This works well with the axon event bus. Circumstance behoves me to employ Kafka as the event bus (auto-configured - axon-kafka-spring-boot-starter); however, events are neither dispatched nor consumed.

How do I go about this issue? Thanks.

One of the main goals of this project is to provide a base framework for avro serialization with axonframework.
To use avro from the axon server dashboard, this requires an osgi plugin to be installed on the axon server.

While the concrete axon specific listeners plugin is part of holixon/axon-avro-serializer, the core functionality (configuring and accessing an confluent registry) should be part of this repo.

This way, we can later just exchange the core plugin (for example to use confluent registry) without providing multiple implementations for axon server.

So the task is: Parallel to the confluent rest client module, provide an osgi bundle that allows running a registry-adapter as a plugin.

Is blocked by: #59

Hello again,

There's a newer issue concerning the Apicurio schema registry adapter and plugins provided as part of the project.

The issue seems to originate from the Schema Registration Component. It uploads and versions my schemas as it should; however, it fails in applying the appropriate schema Id to the Avro Schema in my Apicurio Registry instance...

So, while deserialising the axon message payload, the adapter looks up an artefact of a specific serialVersionUID, first from the cache, then the schema registry (if unavailable). The error now arises since the Schema Id in this instance is TestEvent while the adapter looks up a schema of id:: 6729430080489649277

This error also occurs in the axon-Avro-server-schema-registry-apicurio-plugin installed on the axon server instance as shown here...

While Querying for events stored on the axon server, I get jumbled up records...

I have tried looking for misconfiguration errors on my end, but everything I have implemented follows the documentation (https://www.holixon.io/axon-avro-serializer/snapshot/reference/index.html) to the letter.

Kindly get back to me as soon as possible on possible solutions.

Kind Regards,
Kahiga wa Kiguru.

so we get PRs when lib versions changes

• provide intermediate format GenericRecord for upcaster

Acceptance Criteria

• Have two modules: command and query
• query module uses schema X
• command module uses a newer schema with incompatible change (e.g. a field is added but no default is provided)
• an upcaster exists that is installed in the query part and fixes the incompatibility by setting the default
• the upcaster works on the level of generic record

update docker image version

was: toolisticon

The suffix "-root" is misleading, and I do not like the suffix "-parent". Since the intermediate poms are just used to structure the multi module layout and have no "meaning" nor will ever be imported by other projects, lets just append a "_" to make their names unique for the project.

Hi,
we were looking at using this project in combination with an Axon + Apache Kafka Event Bus setup, but it seems that the documentation is rather lacking and some basic functionality is not given.

For example, given the Getting started page, the @EnableAxonAvroSerializer annotation is not importable.

These are the dependencies that I've included (using Gradle instead of Maven):

implementation "io.holixon.axon.avro:axon-avro-serializer-spring:0.0.5"
implementation "io.holixon.avro:avro-registry-adapter-apicurio:0.0.5"

Has this project been abandoned?

One of the main goals of this project is to provide a base framework for avro serialization with axonframework.
To use avro from the axon server dashboard, this requires an osgi plugin to be installed on the axon server.

While the concrete axon specific listeners plugin is part of holixon/axon-avro-serializer, the core functionality (configuring and accessing an apicurio registry) should be part of this repo.

This way, we can later just exchange the core plugin (for example to use confluent registry) without providing multiple implementations for axon server.

So the task is: Parallel to the apicurio rest client module, provide an osgi bundle that allows running a registry-adapter as a plugin.

The avro single object bytes can not be displayed correctly in axon server cloud.

Idea: Serialize the payload as json and store the schemaId in metaData (see #73).

See https://github.com/holixon/axon-framework-bom

we did a lot of changes, fixes and version updates on the registry adapter, so the next release of the serializer should use them.