Re: Suggestion about syntax of CREATE COLUMN FAMILY
As a starter I also fully agree with this suggestion. You could submit it as feature request to the Cassandra JIRA. 2011/12/12 Stephen Pope stephen.p...@quest.com I’d like to second this. I’ve been working with Cassandra for a good while now, but when I first started little things like this were confusing. ** ** *From:* Don Smith [mailto:dsm...@likewise.com] *Sent:* Friday, December 09, 2011 3:41 PM *To:* user@cassandra.apache.org *Subject:* Suggestion about syntax of CREATE COLUMN FAMILY ** ** Currently, the syntax for creating column families is like this: create column family Users with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type; It's not clear what comparator and default_validation_class refer to. Much clearer would be: create column family Users with *column_name_comparator*=UTF8Type and *column_value_validation_class*=UTF8Type and key_validation_class=UTF8Type; BTW, instead of column_name_comparator, I'd actually prefer column_key_comparator since it seems more accurate to call column names column keys. Don
RE: Suggestion about syntax of CREATE COLUMN FAMILY
FYI, I submitted an enhancement tickethttps://issues.apache.org/jira/browse/CASSANDRA-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel to JIRA about this. The ticket was resolved with the comment: cli is kept around for backwards compatiblity at this point; cqlsh is 'the future.' Don From: Stephen Pope [stephen.p...@quest.com] Sent: Monday, December 12, 2011 6:34 AM To: user@cassandra.apache.org Subject: RE: Suggestion about syntax of CREATE COLUMN FAMILY I’d like to second this. I’ve been working with Cassandra for a good while now, but when I first started little things like this were confusing. From: Don Smith [mailto:dsm...@likewise.com] Sent: Friday, December 09, 2011 3:41 PM To: user@cassandra.apache.org Subject: Suggestion about syntax of CREATE COLUMN FAMILY Currently, the syntax for creating column families is like this: create column family Users with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type; It's not clear what comparator and default_validation_class refer to. Much clearer would be: create column family Users with column_name_comparator=UTF8Type and column_value_validation_class=UTF8Type and key_validation_class=UTF8Type; BTW, instead of column_name_comparator, I'd actually prefer column_key_comparator since it seems more accurate to call column names column keys. Don
Re: Suggestion about syntax of CREATE COLUMN FAMILY
Doesn't CQL have the same issue? http://crlog.info/2011/09/17/cassandra-query-language-cql-v2-0-reference/#Column+Family+Options+(optional) http://www.datastax.com/docs/1.0/references/cql/CREATE_COLUMNFAMILY CREATE COLUMNFAMILY user_events (user text PRIMARY KEY) WITH *comparator*=timestamp AND *default_validation*=int; Do CQL enhancements also belong in the same jira project, or somewhere else? Ernie On Thu, Dec 22, 2011 at 11:51 AM, Don Smith dsm...@likewise.com wrote: FYI, I submitted an enhancement tickethttps://issues.apache.org/jira/browse/CASSANDRA-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanelto JIRA about this. The ticket was resolved with the comment: cli is kept around for backwards compatiblity at this point; cqlsh is 'the future.' Don -- *From:* Stephen Pope [stephen.p...@quest.com] *Sent:* Monday, December 12, 2011 6:34 AM *To:* user@cassandra.apache.org *Subject:* RE: Suggestion about syntax of CREATE COLUMN FAMILY I’d like to second this. I’ve been working with Cassandra for a good while now, but when I first started little things like this were confusing. *From:* Don Smith [mailto:dsm...@likewise.com] *Sent:* Friday, December 09, 2011 3:41 PM *To:* user@cassandra.apache.org *Subject:* Suggestion about syntax of CREATE COLUMN FAMILY Currently, the syntax for creating column families is like this: create column family Users with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type; It's not clear what comparator and default_validation_class refer to. Much clearer would be: create column family Users with *column_name_comparator*=UTF8Type and *column_value_validation_class*=UTF8Type and key_validation_class=UTF8Type; BTW, instead of column_name_comparator, I'd actually prefer column_key_comparator since it seems more accurate to call column names column keys. Don
RE: Suggestion about syntax of CREATE COLUMN FAMILY
I believe you're right!. The change to cli would be an easy fix, I imagine; for backwards compatibility, they'd probably want to allow either the old or new syntax for cli. But I understand their decision not to devote time to a deprecated tool.For cqlsh I hope it's not too late to deprecate the old, unclear syntax. Don From: ehers...@gmail.com [ehers...@gmail.com] Sent: Thursday, December 22, 2011 10:20 AM To: user@cassandra.apache.org Subject: Re: Suggestion about syntax of CREATE COLUMN FAMILY Doesn't CQL have the same issue? http://crlog.info/2011/09/17/cassandra-query-language-cql-v2-0-reference/#Column+Family+Options+(optional) http://www.datastax.com/docs/1.0/references/cql/CREATE_COLUMNFAMILY CREATE COLUMNFAMILY user_events (user text PRIMARY KEY) WITH comparator=timestamp AND default_validation=int; Do CQL enhancements also belong in the same jira project, or somewhere else? Ernie On Thu, Dec 22, 2011 at 11:51 AM, Don Smith dsm...@likewise.commailto:dsm...@likewise.com wrote: FYI, I submitted an enhancement tickethttps://issues.apache.org/jira/browse/CASSANDRA-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel to JIRA about this. The ticket was resolved with the comment: cli is kept around for backwards compatiblity at this point; cqlsh is 'the future.' Don From: Stephen Pope [stephen.p...@quest.commailto:stephen.p...@quest.com] Sent: Monday, December 12, 2011 6:34 AM To: user@cassandra.apache.orgmailto:user@cassandra.apache.org Subject: RE: Suggestion about syntax of CREATE COLUMN FAMILY I’d like to second this. I’ve been working with Cassandra for a good while now, but when I first started little things like this were confusing. From: Don Smith [mailto:dsm...@likewise.commailto:dsm...@likewise.com] Sent: Friday, December 09, 2011 3:41 PM To: user@cassandra.apache.orgmailto:user@cassandra.apache.org Subject: Suggestion about syntax of CREATE COLUMN FAMILY Currently, the syntax for creating column families is like this: create column family Users with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type; It's not clear what comparator and default_validation_class refer to. Much clearer would be: create column family Users with column_name_comparator=UTF8Type and column_value_validation_class=UTF8Type and key_validation_class=UTF8Type; BTW, instead of column_name_comparator, I'd actually prefer column_key_comparator since it seems more accurate to call column names column keys. Don
RE: Suggestion about syntax of CREATE COLUMN FAMILY
I'd like to second this. I've been working with Cassandra for a good while now, but when I first started little things like this were confusing. From: Don Smith [mailto:dsm...@likewise.com] Sent: Friday, December 09, 2011 3:41 PM To: user@cassandra.apache.org Subject: Suggestion about syntax of CREATE COLUMN FAMILY Currently, the syntax for creating column families is like this: create column family Users with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type; It's not clear what comparator and default_validation_class refer to. Much clearer would be: create column family Users with column_name_comparator=UTF8Type and column_value_validation_class=UTF8Type and key_validation_class=UTF8Type; BTW, instead of column_name_comparator, I'd actually prefer column_key_comparator since it seems more accurate to call column names column keys. Don
Suggestion about syntax of CREATE COLUMN FAMILY
Currently, the syntax for creating column families is like this: create column family Users with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type; It's not clear what comparator and default_validation_class refer to. Much clearer would be: create column family Users with column_name_comparator=UTF8Type and column_value_validation_class=UTF8Type and key_validation_class=UTF8Type; BTW, instead of column_name_comparator, I'd actually prefer column_key_comparator since it seems more accurate to call column names column keys. Don
