[FEATURE REQUEST] Support for Avro and Schema Registry about laravel-kafka HOT 4 CLOSED

Hello @robertpcontreras-ts,
This feature is in development process. See #5
I'm planning to release this later today or tomorrow morning.

from laravel-kafka.

@robertpcontreras-ts released on v1.1.0 😄

from laravel-kafka.

We can deserialize a msg without knowing the scehma or topic: in FlixTech\AvroSerializer\Objects\RecordSerializer .
msg in kafka has already information about the schema so can we have this feature in this package? @mateusjunges

so after that we do not need

$registry->addBodySchemaMappingForTopic(
'test-topic',
new \Junges\Kafka\Message\KafkaAvroSchema('bodySchema' , 9 /* , AvroSchema $definition /)
);
$registry->addKeySchemaMappingForTopic(
'test-topic',
new \Junges\Kafka\Message\KafkaAvroSchema('keySchema' , 9 / , AvroSchema $definition */)
);

and it will decode based on message data.

from laravel-kafka.

@mateusjunges any update about above comment?

it's serious/
let me please explain a situation,

we create a command to consume a topic.
then it is consuming and waiting for next message, but meanwhile , producer will produce a new message base on a new version of avro schema, then when application take the next message, cannot decerialize it and throw the FlixTech\AvroSerializer\Objects\Exceptions\AvroDecodingException/app/vendor/flix-tech/avro-serde-php/src/Objects/Exceptions/Exceptions.php:42
Could not decode message. Binary Message (as Hex): "00

so if consumer could know the new message avro schema version and take it , it wouldn't happen.

from laravel-kafka.