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 ECD9311505 for ; Sun, 14 Sep 2014 18:54:33 +0000 (UTC) Received: (qmail 82600 invoked by uid 500); 14 Sep 2014 18:54:33 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 82557 invoked by uid 500); 14 Sep 2014 18:54:33 -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 82546 invoked by uid 99); 14 Sep 2014 18:54:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Sep 2014 18:54:33 +0000 Date: Sun, 14 Sep 2014 18:54:33 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-3122) Rename per-table custom tag property prefix 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-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-3122: ---------------------------------------- Description: I'm not 100% sold on the name of the {{table.custom.\*}} prefix added in ACCUMULO-2841. I think a better name might be {{table.tag.\*}} or similar, and I'm leaning towards that. *Tag* might be better vocabulary to use, especially when discussing the feature in the documentation, and the property prefix name should be consistent with how we refer to the feature. I'm creating this issue to provide a forum for property name suggestions/informal votes/comments, so the name can be solidified before the feature manifests in a release. I don't want to change it to *tag* now, and then tomorrow change it again in favor of a better name. was: I'm not 100% sold on the name of the "table.custom.*" prefix added in ACCUMULO-2841. I think a better name might be "table.tag.*" or similar, and I'm leaning towards that. "Tag" might be better vocabulary to use, especially when discussing the feature in the documentation, and the property prefix name should be consistent with how we refer to the feature. I'm creating this issue to provide a forum for property name suggestions/informal votes/comments, so the name can be solidified before the feature manifests in a release. I don't want to change it to "tag" now, and then tomorrow change it again in favor of a better name. > Rename per-table custom tag property prefix > ------------------------------------------- > > Key: ACCUMULO-3122 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3122 > Project: Accumulo > Issue Type: Sub-task > Components: client > Reporter: Christopher Tubbs > Priority: Trivial > Labels: api, docuentation, naming > Fix For: 1.7.0 > > > I'm not 100% sold on the name of the {{table.custom.\*}} prefix added in ACCUMULO-2841. I think a better name might be {{table.tag.\*}} or similar, and I'm leaning towards that. *Tag* might be better vocabulary to use, especially when discussing the feature in the documentation, and the property prefix name should be consistent with how we refer to the feature. > I'm creating this issue to provide a forum for property name suggestions/informal votes/comments, so the name can be solidified before the feature manifests in a release. I don't want to change it to *tag* now, and then tomorrow change it again in favor of a better name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)