accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (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:31:35 GMT

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

Josh Elser commented on ACCUMULO-2883:
--------------------------------------

bq. user can only read portions of the metadata table for tables they have read or write access.


That helps to isolate users from knowing anything about tables that don't have permission
to, but it still doesn't help the potential leak of sensitive info for rowIDs that the user
might not have access to otherwise see.

[~ecn] has also noted that you could also easily just make calls against the tserver to get
the at tablet boundaries (the response of no data is different than tablet not hosted here).

It doesn't seem like there's a universal solution that doesn't involve delegation through
some other gateway. The thrift proxy server is one example which would do this (again, [~ecn]
pointing this out).

> 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