[
https://issues.apache.org/jira/browse/ACCUMULO-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468652#comment-13468652
]
Billie Rinaldi commented on ACCUMULO-498:
-----------------------------------------
Note that it is possible to have a Key with a visibility that is not a valid
ColumnVisibility (see ACCUMULO-193). How should we handle calls to
getColumnVisibilityParsed() in this case? Just let it throw the error?
I don't think we should parse the CV unless someone asks for it, but I guess we
could store it once someone asks for it, and drop what is stored if the CV
changes.
> 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