You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2016/09/15 22:04:20 UTC

[jira] [Resolved] (KUDU-565) Tests for client where keys fall on tablet boundaries

     [ https://issues.apache.org/jira/browse/KUDU-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved KUDU-565.
-------------------------------------
          Resolution: Invalid
            Assignee: Dan Burkert
       Fix Version/s: n/a
    Target Version/s:   (was: GA)

Thanks Dan, resolving as invalid then.

> Tests for client where keys fall on tablet boundaries
> -----------------------------------------------------
>
>                 Key: KUDU-565
>                 URL: https://issues.apache.org/jira/browse/KUDU-565
>             Project: Kudu
>          Issue Type: Task
>          Components: client, test
>    Affects Versions: M5
>            Reporter: Todd Lipcon
>            Assignee: Dan Burkert
>            Priority: Critical
>             Fix For: n/a
>
>
> I think we may have some bugs when a row falls exactly on a tablet boundary. Most of our correctness testing uses auto-generated split keys in a big key space, but this means it's unlikely we insert something exactly on the boundary. Looking at the code, I think there's some sloppiness where in some cases we consider upper bounds to be inclusive (eg on scans) and in other places exclusive (eg on tablet ranges).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)