There can be certain configuration requirements where the connector user's default schema is different from where the user is permitted to create the log mining flush table, and this creates a problem both with the automatic creation and the automatic check of the table's existence.

The log.mining.flush.table.name should permit including an optional schema, using the format of schema.table.

This should ease this corner case and make the flush table logic easier to manage without imposing unnecessary requirements on the user account.