accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-2059) Namespace constraints easily get clobbered by table constraints
Date Wed, 18 Dec 2013 21:15:08 GMT
John Vines created ACCUMULO-2059:
------------------------------------

             Summary: 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.4#6159)

Mime
View raw message