On Tue, Aug 18, 2009 at 8:24 PM, Jonathan Ellisjbel...@gmail.com wrote:
That's really outside our scope here. Anyone who wants to write docs
in a non-English language is welcome to start another thread to
discuss terminology in that language, but we shouldn't hold up the
canonical English
Did you read the previous thread about this?
http://markmail.org/thread/qbocotgkan4mg73w
I don't think your proposals are too good...I have a new proposal
based on feedback in the previous thread, that I will send soon. But I
wanted some comments on the misconceptions themselves.
Evan
On Tue,
On Tue, Aug 18, 2009 at 10:36 AM, Evan Weaverewea...@gmail.com wrote:
Did you read the previous thread about this?
http://markmail.org/thread/qbocotgkan4mg73w
I don't think your proposals are too good...I have a new proposal
based on feedback in the previous thread, that I will send soon.
On Mon, 2009-08-17 at 15:32 -0700, Mark McBride wrote:
My first attempt at a revamped data model wiki page is up here
http://wiki.apache.org/cassandra/DataModel2
I think you are on the right track. Very nice.
--
Eric Evans
eev...@rackspace.com
This is a good discussion.
I would like to add that whatever English names we end up with we
should also get non-English versions of those words as part of our
process.
I say process because there may be a perfect word in Hebrew, Nigerian,
or other language we can borrow that implies the perfect
On Aug 18, 2009, at 11:51 AM, Wilson Mar wrote:
I say process because there may be a perfect word in Hebrew, Nigerian,
or other language we can borrow that implies the perfect nuance we
need.
I've found Finnish to have pronounceable English looking words that
have great meanings. For
While I interpret Evan as arguing against using RDB terms like row and
column, I would favor keeping those terms. Cassandra's data model is
typically *initially* described as a table--without relational
aspects!--and then the distinction of its storage strategy
(column-oriented, mostly, sort of,
Ok, here are the common Cassandra misconceptions, and their sources,
gleaned from experience and talking to various people.
Not listed in any particular order.
1. A key is global, and data in different column families must be related.
- BigTable paper
- key precedence in Thrift API
2. Table
I find the diagrams of Evan and folks
(http://blog.evanweaver.com/files/cassandra/twitter.jpg) much easier
to grok than any particular naming scheme. Annotating that diagram
with specific implementations or constraints, like your wiki page, is
a great addition.
.. Adam
On Mon, Aug 17, 2009 at
I've been thinking about this for a number of days, and again, while I am not a
developer I thought I might toss in a proposal if that's okay.
Since putting together a schema diagram and having a number of people review
it, I think a change is warranted. Too many people are coming from the RDBMS
10 matches
Mail list logo
