Return-Path: 
 <cassandra-commits-return-3446-apmail-incubator-cassandra-commits-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-cassandra-commits-archive@minotaur.apache.org
Received: (qmail 68333 invoked from network); 30 Jul 2009 05:16:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 30 Jul 2009 05:16:38 -0000
Received: (qmail 14192 invoked by uid 500); 30 Jul 2009 05:16:38 -0000
Delivered-To: apmail-incubator-cassandra-commits-archive@incubator.apache.org
Received: (qmail 14160 invoked by uid 500); 30 Jul 2009 05:16:38 -0000
Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
List-Help: <mailto:cassandra-commits-help@incubator.apache.org>
List-Unsubscribe: <mailto:cassandra-commits-unsubscribe@incubator.apache.org>
List-Post: <mailto:cassandra-commits@incubator.apache.org>
List-Id: <cassandra-commits.incubator.apache.org>
Reply-To: cassandra-dev@incubator.apache.org
Delivered-To: mailing list cassandra-commits@incubator.apache.org
Received: (qmail 14150 invoked by uid 99); 30 Jul 2009 05:16:38 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jul 2009 05:16:38 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jul 2009 05:16:35 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id CA3B4234C044
	for <cassandra-commits@incubator.apache.org>;
 Wed, 29 Jul 2009 22:16:14 -0700 (PDT)
Message-ID: <1322793566.1248930974812.JavaMail.jira@brutus>
Date: Wed, 29 Jul 2009 22:16:14 -0700 (PDT)
From: "Michael Greene (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-271) Rename <table> to <keyspace>
In-Reply-To: <541947641.1246463389658.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/CASSANDRA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Greene updated CASSANDRA-271:
-------------------------------------

    Attachment: 271_stress.diff

Oops, forgot stress test.

> Rename <table> to <keyspace>
> ----------------------------
>
>                 Key: CASSANDRA-271
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-271
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 271-3.patch, 271-v2.patch, 271-v4.patch, 271.patch, 271_stress.diff
>
>
> Using <table> in the configuration file to mean "the unit over which key/cf pairs are unique" is not useful.  It confuses both people from a relational background (the vast -- vast! -- majority of users) and people from a Bigtable/HBase/Hypertable background, because Cassandra's data model, while closer to BT than MySQL, is still different enough to be confusing.  Both of these mistaken assumptions of familiarity have caused me problems explaining Cassandra to actual users.  We are the newcomers by 30 years in one case and 2 years in the other; insisting on our own, different interpretation of a familiry term seems silly.
> It's possible that calling it KeySpace will not solve the problem, but I see this as a situation where the status quo does us no good at all -- the only connotations <table> has for people are WRONG -- and changing it has a chance of improving the situation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.