Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8405817723 for ; Sat, 4 Apr 2015 02:42:34 +0000 (UTC) Received: (qmail 81509 invoked by uid 500); 4 Apr 2015 02:42:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 81476 invoked by uid 500); 4 Apr 2015 02:42:34 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 81460 invoked by uid 99); 4 Apr 2015 02:42:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2015 02:42:34 +0000 Date: Sat, 4 Apr 2015 02:42:34 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2059) Namespace constraints easily get clobbered by table constraints MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-2059: --------------------------------- Fix Version/s: (was: 1.7.0) 1.8.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 > Affects Versions: 1.6.0 > Reporter: John Vines > Fix For: 1.8.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.3.4#6332)