hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17486) Tighten the contract for batch client methods
Date Wed, 18 Jan 2017 23:19:26 GMT

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

stack updated HBASE-17486:
--------------------------
    Assignee: Michael Axiak

> Tighten the contract for batch client methods
> ---------------------------------------------
>
>                 Key: HBASE-17486
>                 URL: https://issues.apache.org/jira/browse/HBASE-17486
>             Project: HBase
>          Issue Type: Bug
>          Components: API
>            Reporter: Michael Axiak
>            Assignee: Michael Axiak
>            Priority: Trivial
>              Labels: documentation
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17486.patch
>
>
> Right now, the API documentation for Table#get(List) and Table#batch(List, Result[])
both leave open the possibility for the ordering of the result array to be independent of
the input actions.
> In at least the batch method case, ordering of the result array is important in order
to know which partial requests failed in the event of an exception. Since that contact is
required in the batch case, I think it should be extended to the get(List) case as well to
make the API easier.



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

Mime
View raw message