cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3779) need forked language document
Date Tue, 24 Apr 2012 16:39:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260688#comment-13260688
] 

Sylvain Lebresne edited comment on CASSANDRA-3779 at 4/24/12 4:37 PM:
----------------------------------------------------------------------

Forgot to say: The doc is trying to stick to a vocabulary that I think make sense for CQL3.
In particular, it does not respect the current Cassandra vocabulary. For instance, the notion
of column and row in the document are the ones of SQL, *not* the one of our internal representation.
I also use the term table instead of column family systematically. While I understand this
may be confusing for current users of Cassandra, I think this happens to be a very good fit
to CQL3 and imho trying to do otherwise would make it very hard to explain CQL3. Besides,
I doubt Cassandra users have already forgotten the notion of columns and rows in SQL, so the
confusion should be minimal as long as we make the context clear.

But this means I'll probably add a small warning at the beginning of the doc.
                
      was (Author: slebresne):
    Forgot to say: The doc is trying to a vocabulary that I think make sense for CQL3. In
that respect, it does not respect the current Cassandra vocabulary. For instance, the notion
of column and row in the document are the ones of SQL, *not* the one of our internal representation.
I also use the term table instead of column family systematically. While I understand this
may be confusing for current user of Cassandra, I think this happens to be a very good fit
to CQL3 and imho trying to do otherwise would make it very hard to explain CQL3. Besides,
I doubt Cassandra users have already forgotten the notion of columns and rows in SQL, so the
confusion should be minimal as long as we make the context clear.

But this means I'll probably add a small warning at the beginning of the doc.
                  
> need forked language document
> -----------------------------
>
>                 Key: CASSANDRA-3779
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3779
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1.0
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1.1
>
>
> The language doc ({{doc/cql/CQL.textile}}) needs to be forked for CQLv3 and updated accordingly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message