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.