You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/02/05 23:58:08 UTC
[jira] [Commented] (ACCUMULO-2059) Namespace constraints easily get
clobbered by table constraints
[ https://issues.apache.org/jira/browse/ACCUMULO-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892717#comment-13892717 ]
Christopher Tubbs commented on ACCUMULO-2059:
---------------------------------------------
I'm fine with bumping, especially if the best fix is to address the entire hierarchy as a whole.
> 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)