Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 6 Mar 2015 23:18:38 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12778359.1425077455000.25923.1425683918921@Atlassian.JIRA>
In-Reply-To: <JIRA.12778359.1425077455000@Atlassian.JIRA>
References: <JIRA.12778359.1425077455000@Atlassian.JIRA>
 <JIRA.12778359.1425077455860@arcas>
Subject: [jira] [Commented] (CASSANDRA-8878) Counter Tables should be more
 clearly identified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-8878?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
14351104#comment-14351104 ]=20

Jonathan Ellis commented on CASSANDRA-8878:
-------------------------------------------

I'm fine with that.  We have limitations on other kinds of mixed batches (e=
.g. when LWT are involved) and I think that's a much easier sell than separ=
ate tables entirely.

> Counter Tables should be more clearly identified
> ------------------------------------------------
>
>                 Key: CASSANDRA-8878
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8878
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Micha=C3=ABl Figui=C3=A8re
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 3.0
>
>
> Counter tables are internally considered as a particular kind of table, d=
ifferent from the regular ones. This counter specific nature is implicitly =
defined by the fact that columns within a table have the {{counter}} data t=
ype. This nature turns out to be persistent over the time, that is if the u=
ser do the following:
> {code}
> CREATE TABLE counttable (key uuid primary key, count counter);
> ALTER TABLE counttable DROP count;
> ALTER TABLE counttable ADD count2 int;
> {code}=20
> The following error will be thrown:
> {code}
> Cannot add a non counter column (count2) in a counter column family
> {code}
> Even if the table doesn't have any counter column anymore. This implicit,=
 persistent nature can be challenging to understand for users (and impossib=
le to infer in the case above). For this reason a more explicit declaration=
 of counter tables would be appropriate, as:
> {code}
> CREATE COUNTER TABLE counttable (key uuid primary key, count counter);
> {code}
> Besides that, adding a boolean {{counter_table}} column in the {{system.s=
chema_columnfamilies}} table would allow external tools to easily different=
iate a counter table from a regular one.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)