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?

2.2.1

What is the connector configuration?

"config" : {
"connector.class" : "io.debezium.connector.mysql.MySqlConnector",
"database.hostname" : host_name,
"database.port" : port_number
"database.user" : "${DB_USER}",
"database.password" : "${DB_PASSWORD}",
"database.server.name" : server_name,
"database.server.id" : server_id,
"database.include.list" : db_schema_name,
"table.include.list" : some_table_list,
"snapshot.include.collection.list": some_table_list,
"topic.prefix" : prefix
"topic.creation.enable" : "true",
"topic.creation.default.replication.factor" : 3,
"topic.creation.default.partitions" : 6,
"tasks.max" : 1,
"snapshot.mode" : "when_needed",
"snapshot.isolation.mode" : "read_committed",
"snapshot.max.threads" : 2,
"include.schema.changes" : "true",
"read.only" : "true",
"key.converter" : "io.confluent.connect.avro.AvroConverter",
"value.converter" : "io.confluent.connect.avro.AvroConverter",
"producer.override.max.request.size" : 8000000,
"key.converter.schema.registry.url" : schema_registry_endpoint,
"value.converter.schema.registry.url" : schema_registry_endpoint,
"key.converter.basic.auth.credentials.source" : "USER_INFO",
"key.converter.basic.auth.user.info" : "${SCHEMA_API_KEY}:${SCHEMA_SECRET_KEY}",
"value.converter.basic.auth.credentials.source" : "USER_INFO",
"value.converter.basic.auth.user.info" : "${SCHEMA_API_KEY}:${SCHEMA_SECRET_KEY}",
"database.ssl.mode" : "preferred",
"database.allowPublicKeyRetrieval" : "true",
"schema.history.internal.kafka.topic" : dbhistory_topic,
"schema.history.internal.kafka.bootstrap.servers" : bootstrap_server_endpoint,
"schema.history.internal.consumer.security.protocol" : "SASL_SSL",
"schema.history.internal.consumer.sasl.mechanism" : "PLAIN",
"schema.history.internal.consumer.sasl.jaas.config" : "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"${KAFKA_API_KEY}\" password=\"${KAFKA_SECRET_KEY}\";",
"schema.history.internal.consumer.ssl.endpoint.identification.algorithm" : "https",
"schema.history.internal.producer.security.protocol" : "SASL_SSL",
"schema.history.internal.producer.sasl.mechanism" : "PLAIN",
"schema.history.internal.producer.sasl.jaas.config" : "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"${KAFKA_API_KEY}\" password=\"${KAFKA_SECRET_KEY}\";",
"schema.history.internal.producer.ssl.endpoint.identification.algorithm" : "https",
"signal.enabled.channels" : "kafka",
"signal.kafka.topic" : prefix-server_name-signal,
"signal.kafka.groupId" : "prefix-server_name-signal",
"signal.kafka.bootstrap.servers" : "bootstrap_server",
"signal.kafka.poll.timeout.ms" : "1000",
"signal.consumer.security.protocol" : "SASL_SSL",
"signal.consumer.sasl.mechanism" : "PLAIN",
"signal.consumer.sasl.jaas.config" : "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"${KAFKA_API_KEY}\" password=\"${KAFKA_SECRET_KEY}\";",
"signal.consumer.ssl.endpoint.identification.algorithm" : "https"
}

What is the captured database version and mode of depoyment?

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

mysql 8.0.29, deployed in cloud through k8s

What behaviour do you expect?

Expect the ALTER user DDL to be parsed and connector to not fail

What behaviour do you see?

Our Debezium connector fails with the below error -

Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'ALTER USER 'some_user_name'@'some_IP_address' IDENTIFIED WITH 'mysql_native_password' AS 'some_password' RETAIN CURRENT PASSWORD'
nmismatched input 'RETAIN' expecting {\u003cEOF\u003e, '-'}

Above is just a snippet of the error trace, can provide a longer version if needed 

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

(Ideally, also verify with latest Alpha/Beta/CR version)

I have not been able to try the latest version yet unfortunately

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

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

By issuing the same ALTER USER command mentioned above.

Feature request or enhancement

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

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

<Your answer>

Implementation ideas (optional)

<Your answer>