Any news on that one? The bug still exists using Spring Boot 3.1 together with hibernate core 6.2.2.Final or 6.2.4.Final… The custom schema provider gets loaded but the configured custom shema filter is never used (no calls to “includeTable”)…

The hibernate SchemaManagementToolCoordinator uses DefaultShemaFilter.INSTANCE instead of the configured one… so the custom schema filter is never used…