[jira] [Resolved] (KUDU-1715) Add a way to set ReplicaSelection to the java client

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

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

Jean-Daniel Cryans resolved KUDU-1715.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

Fixed in a7fd4fc85c0878570a5ab51a8e28275fd4459ff5.

> Add a way to set ReplicaSelection to the java client
> ----------------------------------------------------
>
>                 Key: KUDU-1715
>                 URL: https://issues.apache.org/jira/browse/KUDU-1715
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: 1.0.0
>            Reporter: David Alves
>            Assignee: Jean-Daniel Cryans
>             Fix For: 1.1.0
>
>
> On the C++ client we're able to set a ReplicaSelection policy on the KuduScanner that hints at which replica should be chosen to perform the scan:
> {code}
> Status SetSelection(KuduClient::ReplicaSelection selection)
> {code}
> ... where ReplicaSelection can have the following values:
> {code}
>     LEADER_ONLY,      ///< Select the LEADER replica.
>     CLOSEST_REPLICA,  ///< Select the closest replica to the client,
>                       ///< or a random one if all replicas are equidistant.
>     FIRST_REPLICA     ///< Select the first replica in the list.
> {code}
> Having the same functionality in the java client will increase our confidence in our tests that use and would be helpful for perf, since it's pretty common for leaders to get clustered and the java client only scans from the leader currently.



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