accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Fuchs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2883) Add API method(s) that support fetching currently assigned locations for tablets
Date Thu, 06 Nov 2014 18:38:35 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200616#comment-14200616
] 

Adam Fuchs commented on ACCUMULO-2883:
--------------------------------------

[~elserj] One way to look at this is that there is a certain amount of trust given to any
app that is allowed to access Accumulo. Handling Accumulo's metadata is included in that trust.
A permission model protecting metadata might encourage apps not to simply pass that information
on but first consider the potential sensitivity. Sorry to speak philosophically, but I don't
have a better solution either in the general case.

> 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)

Mime
View raw message