the same key should not be returned more than once to clients

Using a complicated iterator configuration, a user experienced a bug in which their iterator returned the same key repeatedly. I suggested that we have the client library detect this case and throw an error. However, we have allowed multiple identical keys to be stored and returned in the past. I would like to change that policy to be able to implement this check.