[
https://issues.apache.org/jira/browse/ACCUMULO-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015217#comment-15015217
]
ASF GitHub Bot commented on ACCUMULO-2883:
------------------------------------------
GitHub user keith-turner opened a pull request:
https://github.com/apache/accumulo/pull/53
ACCUMULO-2883 Added locating tablets to API
I have modified Gora to use this update in a [branch][2]. I plan to
experiment with modifying [geowave][1] to use this new API before pusing to
master.
[1]: https://github.com/ngageoint/geowave
[2]: https://github.com/keith-turner/gora/tree/GORA-414-180
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/keith-turner/accumulo ACCUMULO-2883
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/accumulo/pull/53.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #53
----
commit f89e386148173dbd902765da711c0c553fd37fa6
Author: Keith Turner <[email protected]>
Date: 2015-11-13T04:31:22Z
ACCUMULO-2883 Added locating tablets to API
----
> Add API method(s) that support fetching currently assigned locations for
> tablets
> --------------------------------------------------------------------------------
>
> Key: ACCUMULO-2883
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2883
> Project: Accumulo
> Issue Type: New Feature
> Components: client
> Reporter: Josh Elser
> Assignee: Keith Turner
> Fix For: 1.8.0
>
>
> TabletLocator already exists, but isn't officially a part of the "public API"
> and is clunky for users to invoke. In trying to co-locate external processes
> with the tabletservers that are hosting some data, it would be nice to have
> some means that users can invoke that will return them these assignments.
> Memory concerns are an issue for tables with many splits (e.g. avoiding
> creating a Set of 100k tablet locations for a table), but we also want to
> provide the ability to ask pointed questions. Likely building something that
> accepts a Range (or Collection<Range>) would be best.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)