Creating an Oracle connector with a table.include.list that includes spaces after a comma leads to that specific table not being matched by the LogMiner query.

Example configuration:

"table.include.list": "DEBEZIUM.TAB1, DEBEZIUM.TAB2"
"log.mining.query.filter.mode": "in"

In this case, only TAB1 will be matched, TAB2 will not match any results from the redo logs.

Similarly, the schema include/exclude and user include/exclude lists are affected.