[
https://issues.apache.org/jira/browse/ACCUMULO-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706191#comment-13706191
]
Christopher Tubbs commented on ACCUMULO-1006:
---------------------------------------------
I don't see much of a reason to touch it in 1.5.1 either. We can make these
improvements in future versions. It's all internal code, so there's no end-user
motivation to fix it in a previous version. It will be most useful as part of
ACCUMULO-1288.
> Add test for VisibilityParseException
> -------------------------------------
>
> Key: ACCUMULO-1006
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1006
> Project: Accumulo
> Issue Type: Improvement
> Components: tserver
> Affects Versions: 1.4.2, 1.5.0
> Reporter: Christopher Tubbs
> Assignee: Keith Turner
> Fix For: 1.5.1, 1.6.0
>
>
> I'm not sure this exception can ever actually happen. I think
> ColumnVisibility throws BadArgumentException in all the cases where the
> VisibilityParseException would have been thrown. It's somewhat unfortunate
> that the BadArgumentException is the RuntimeException, and the checked
> exception can never happen.
> We need a test to see if we can make VisibilityParseException happen when
> BadArgumentException doesn't, and possibly do something about
> BadArgumentException, by either wrapping it with a checked exception, or
> something else to reflect the fact that it's more likely to happen than
> VisibilityParseException.
--
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
