[
https://issues.apache.org/jira/browse/KUDU-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830971#comment-15830971
]
Todd Lipcon commented on KUDU-1713:
-----------------------------------
I started writing some more thorough notes here:
https://docs.google.com/document/d/1NEAYaurHXmPd63XHfc7vCNq4Dn6SgupDSImfwc4ujXU/edit?usp=sharing
> 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
> Labels: impala
>
> 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.4#6332)
