Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16864 ( https://hibernate.atlassian.net/browse/HHH-16864?atlOrigin=eyJpIjoiODRiNz... ) Re: JPA Criteria queries do not conform to JPA spec when distinct=false ( https://hibernate.atlassian.net/browse/HHH-16864?atlOrigin=eyJpIjoiODRiNz... ) Conformance is determined by running the JPA TCK with the JPA provider as implementation, and ORM 6 passes that TCK. Calling distinct(false) has no impact as that is the default. What you are complaining about is the change in behavior that is documented in the migration guide ( https://github.com/hibernate/hibernate-orm/blob/6.0/migration-guide.adoc#... ). If you can give us a good use case for the behavior you seem to desire, we can talk about it, but until then, I’ll close this issue as doing this was a deliberate decision. ( https://hibernate.atlassian.net/browse/HHH-16864#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16864#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100233- sha1:f5b6255 )