Even if detecting it’s fairly simple to detect if the write failure was produced by a duplicated key, it’s not so simple to detect which key was duplicated because, as far as I’m concerned, the only way it’s extract it from the error message string, which is error  prone and can easily break with an driver update. So, I will be very happy to see a new method that easily allows to know the key at fault when this kind of error happens.