You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/04/11 00:40:41 UTC

[jira] [Resolved] (KUDU-1713) Client API to indicate the target tablet server for inserts

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

Todd Lipcon resolved KUDU-1713.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0

> Client API to indicate the target tablet server for inserts
> -----------------------------------------------------------
>
>                 Key: KUDU-1713
>                 URL: https://issues.apache.org/jira/browse/KUDU-1713
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.0.0
>            Reporter: Matthew Jacobs
>            Assignee: Todd Lipcon
>              Labels: impala
>             Fix For: 1.4.0
>
>
> Impala (and presumably other engines) can more efficiently insert if its own data shuffling can place data on the same nodes that the destination tablet lives on, to avoid another network transfer from the client. Ideally the client API can take a row and return the destination tablet/tserver.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)