accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1527) the same key should not be returned more than once to clients
Date Fri, 21 Jun 2013 16:10:21 GMT


Christopher Tubbs commented on ACCUMULO-1527:

I think this is sensible to implement, because client code can never rely on getting back
more than one copy of a given key. If the key comes at the end of one batch, the client will
resume with the next key anyway. So client code cannot rely on more than one key with the
same timestamp existing. Because of this, any client code reliance on this behavior is probably
a bug. In the worst case, I imagine that enforcing this will simply expose those existing
bugs in client code.
> the same key should not be returned more than once to clients
> -------------------------------------------------------------
>                 Key: ACCUMULO-1527
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>            Reporter: Eric Newton
>            Priority: Minor
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message