In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

MySQL Connector and version 3.2

What is the connector configuration?

<Your answer>

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

<Your answer>

What behavior do you expect?

The incoming geometry data should be able to converted into a hex coded wkb or ewkb format based on the configuration properties.

Do you see the same behaviour using the latest released Debezium version?

No, the expected behaviour is not there in the latest Debezium version.

Do you have the connector logs, ideally from start till finish?

Yes

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Handling of geometry datatype into hex coded string in wkb and ewkb format

Implementation ideas (optional)

A custom converter which handles the incoming geometry data and converts it into hex coded string of wkb or ewkb values based on the config properties