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?

Embedded Debezium with mysql connector 2.3.2

What is the connector configuration?

Relevant ones are

 
.with(RelationalDatabaseConnectorConfig.COLUMN_INCLUDE_LIST, "....")
 
and,
 
.with(RelationalDatabaseConnectorConfig.SNAPSHOT_SELECT_STATEMENT_OVERRIDES_BY_TABLE, "table1")
.with(RelationalDatabaseConnectorConfig.SNAPSHOT_SELECT_STATEMENT_OVERRIDES_BY_TABLE + ".table1",
"SELECT id, userId, officeId, status FROM Table1 t WHERE au.status NOT IN (1, 2) AND t.userId IS NOT NULL")

What is the captured database version and mode of depoyment?

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

Mysql 5.7

What behaviour do you expect?

I'd expect Debezium to allow both configurations to work together so that I can specify which columns are fetched from DB in the select override. Apparently, this is supported for SQL server already.

What behaviour do you see?

Only one option is allowed

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

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

Yes

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

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

Not relevant since it is a known limitation.

How to reproduce the issue using our tutorial deployment?

Use the suggested configuration.

Feature request or enhancement

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

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

Will allow us to do optimized initial snapshotting.

Implementation ideas (optional)