The meaning/effect of the 'schema' attribute on the @javax.persistence.Table has changed between 5.0.1 and 5.0.2.

Our entity classes are annotated with @Table(name='my_table', schema="my_schema") and upto and including Hibernate 5.0.1 this worked whether it was using a MySQL or SQL Server backend. However, since 5.0.2 this now breaks with a table not found exception. If the catalog attribute is used rather than schema then it works again with MySQL. I wouldn't expect a point release of Hibernate to alter the semantics of such a core element of the mapping configuration.

I've had a look through the changelog in Jira for the 5.0.2 and can't see anything relating to this change, so can only assume that this is an inadvertent side effect of another change.