[
https://issues.apache.org/jira/browse/ACCUMULO-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882202#comment-13882202
]
Christopher Tubbs commented on ACCUMULO-2059:
---------------------------------------------
I suppose it is true that it's not technically a new problem entirely, but
namespaces do add more visibility to the feature. Perhaps we should just focus
on the extra visibility namespaces add to this problem, rather than fix the
hierarchy clobbering entirely, for 1.6.0?
> Namespace constraints easily get clobbered by table constraints
> ---------------------------------------------------------------
>
> Key: ACCUMULO-2059
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2059
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: John Vines
> Fix For: 1.6.0
>
>
> This is why ShellServerIT#namespaces is failing currently. When you create a
> table with the default configurations, that includes a
> DefaultKeySizeConstraint at constraint.1. This overlaps the namespaces
> defined constraint.1, which is a NumericValueConstraint for the test.
> The issue is I'm not sure if this is accepted behavior or not. Constraint
> settings are already sorta wonky, but this is not the time to rewrite it.
> Before I fix it, I just need to know if that is tolerable behavior or if we
> want namespace constraints to start at a different value, like constraint.101
> to minimize impact. Thoughts are requested.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
