[
https://issues.apache.org/jira/browse/ACCUMULO-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200183#comment-14200183
]
Adam Fuchs commented on ACCUMULO-2883:
--------------------------------------
We also need to consider security implications here. The tablet splits are
automatically generated from row identifiers in the data, so knowledge of
tablet splits carries some information about keys in table. That information is
already available to clients under the covers, but there may be room for some
sort of permission model on metadata if we plan on exposing this more publicly.
> 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: Sub-task
> Components: client
> Reporter: Josh Elser
> Fix For: 1.7.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)
