Maksym.Tsybulskyi ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=60a3960... ) *commented* on HHH-9662 ( https://hibernate.atlassian.net/browse/HHH-9662?atlOrigin=eyJpIjoiNDlkMGU... ) Re: IllegalArgumentException when composite ID has IDENTITY generated value ( https://hibernate.atlassian.net/browse/HHH-9662?atlOrigin=eyJpIjoiNDlkMGU... ) We faced the same issue working with Vitess. We used a composite key to have a sharding key as a necessary part. Unfortunately, it’s impossible to use the SEQUENCE strategy with Vitess so this fix is essential for us. Is it any estimation of when the fix will be ready? I see that the task is “In Progress“ from the end of 2019. ( https://hibernate.atlassian.net/browse/HHH-9662#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-9662#add-comment?atlOrigin=eyJ... ) 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#100206- sha1:4ed3dc7 )