accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Brassard (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-498) Key.getColumnVisibility() should return a ColumnVisibility, not a Text
Date Thu, 04 Oct 2012 14:23:47 GMT

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

Luke Brassard commented on ACCUMULO-498:
----------------------------------------

So it seems that a decision needs to be made about efficiency and really whether we want to
give up speed or space. The speed sacrifice will only come when users want to get a ColumnVisibility
directly. On the other hand, the space would get eaten whether or not the user cared about
what type was passed back.

I did look into the option of adding a set(byte[] expression) method to the ColumnVisibility
class to allow for reuse and then allowing for the passing of a ColumnVisibility object into
the getColumnVisibilityParsed() method. It seems like there's not much to be gained there
since the main cost of creating that object and the associated tree will still be there.
                
> Key.getColumnVisibility() should return a ColumnVisibility, not a Text
> ----------------------------------------------------------------------
>
>                 Key: ACCUMULO-498
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-498
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.0, 1.3.5
>            Reporter: John Vines
>            Assignee: Luke Brassard
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 1.5.0
>
>         Attachments: ACCUMULO-498.patch
>
>
> Currently getColumnVisibility() returns a Text. This doesn't make a lot of sense, since
all other methods dealing with column visibilities use the ColumnVisibility object. We should
use that instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message