[Cassandra Wiki] Update of "API" by JonathanEllis

2016-06-12 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for 
change notification.

The "API" page has been changed by JonathanEllis:
https://wiki.apache.org/cassandra/API?action=diff=40=41

Comment:
point to http://cassandra.apache.org/doc/cql3/CQL.html

  == CQL ==
- The preferred interface to Cassandra 1.2 and 2.0 is CQL. There is a quick 
introduction in GettingStarted and 
[[http://www.datastax.com/documentation/cql/3.1/webhelp/index.html|full 
documentation by DataStax]].
+ Cassandra offers a SQL-inspired interface called CQL. The primary difference 
from SQL is the emphasis on denormalization (via Collections) over Joins.  
  
- To use CQL effectively you should also understand 
[[http://www.datastax.com/docs/1.2/ddl/index|Cassandra data modeling]].
+ There is a quick introduction in GettingStarted and 
[[http://cassandra.apache.org/doc/cql3/CQL.html|full documentation here]].
  
+ To use CQL effectively you should also understand the [DataModel].
+ 
- If you plan to write a [[ClientOptions|CQL client]], you should also read 
about the communication 
[[https://github.com/apache/cassandra/blob/cassandra-1.2/doc/native_protocol.spec|protocol
 specification]].  Clients do not need to parse CQL, so you shouldn't need to 
know the details of the [[http://cassandra.apache.org/doc/cql3/CQL.html|antlr 
grammar]]
+ If you plan to write a [[ClientOptions|CQL client]], you should also read 
about the communication 
[[https://github.com/apache/cassandra/blob/trunk/doc/native_protocol_v4.spec|protocol
 specification]].  Clients do not need to parse CQL, so you shouldn't need to 
know the details of the [[http://cassandra.apache.org/doc/cql3/CQL.html|antlr 
grammar]]
  
  == Thrift ==
- You can read about the legacy Thrift RPC API [[API10|here]].
+ You can read about the deprecated Thrift RPC API [[API10|here]].
  
  {{https://c.statcounter.com/9397521/0/fe557aad/1/|stats}}
  


[Cassandra Wiki] Update of API by JonathanEllis

2013-11-13 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The API page has been changed by JonathanEllis:
https://wiki.apache.org/cassandra/API?action=diffrev1=39rev2=40

Comment:
link GettingStarted and fix DS docs link

  == CQL ==
- The preferred interface to Cassandra 1.2 and 2.0 is CQL. !DataStax has 
documentation for [[javascript:void(0);/*1368935502273*/|CQL and cqlsh]], and 
the language grammar is [[http://cassandra.apache.org/doc/cql3/CQL.html|here]].
+ The preferred interface to Cassandra 1.2 and 2.0 is CQL. There is a quick 
introduction in GettingStarted and 
[[http://www.datastax.com/documentation/cql/3.1/webhelp/index.html|full 
documentation by DataStax]].
  
- To use CQL you should also understand 
[[http://www.datastax.com/docs/1.2/ddl/index|Cassandra data modeling]].
+ To use CQL effectively you should also understand 
[[http://www.datastax.com/docs/1.2/ddl/index|Cassandra data modeling]].
  
- If you plan to write a [[ClientOptions|CQL client]], you should also read 
about the communication 
[[https://github.com/apache/cassandra/blob/cassandra-1.2/doc/native_protocol.spec|protocol
 specification]].
+ If you plan to write a [[ClientOptions|CQL client]], you should also read 
about the communication 
[[https://github.com/apache/cassandra/blob/cassandra-1.2/doc/native_protocol.spec|protocol
 specification]].  Clients do not need to parse CQL, so you shouldn't need to 
know the details of the [[http://cassandra.apache.org/doc/cql3/CQL.html|antlr 
grammar]]
  
  == Thrift ==
  You can read about the legacy Thrift RPC API [[API10|here]].


[Cassandra Wiki] Update of API by JonathanEllis

2010-04-06 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The API page has been changed by JonathanEllis.
http://wiki.apache.org/cassandra/API?action=diffrev1=52rev2=53

--

  == Overview ==
- The Cassandra Thrift API changed between [[API03|0.3]], [[API04|0.4]], 0.5 
and [[API06|0.6]]; this document explains the 0.5 version with annotations for 
the changes in 0.6.
+ The Cassandra Thrift API changed substantially after [[API03|0.3]], with 
minor, backwards-compatible changes for [[API04|0.4]], 0.5 and [[API06|0.6]]; 
this document explains the 0.5 version with annotations for the changes in 0.6.
  
  Cassandra's client API is built entirely on top of Thrift. It should be noted 
that these documents mention default values, but these are not generated in all 
of the languages that Thrift supports.  Full examples of using Cassandra from 
Thrift, including setup boilerplate, are found on ThriftExamples.  Higher-level 
clients are linked from ClientOptions.
  


[Cassandra Wiki] Update of API by JonathanEllis

2010-04-01 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The API page has been changed by JonathanEllis.
http://wiki.apache.org/cassandra/API?action=diffrev1=50rev2=51

--

  == Overview ==
  The Cassandra Thrift API changed between 0.3, 0.4, 0.5 and 0.6; this document 
explains the 0.5 version with annotations for the changes in 0.6. The 
[[API03|0.3 API]] and [[API04|0.4 API]] are archived for reference.
  
- Cassandra's client API is built entirely on top of Thrift. It should be noted 
that these documents mention default values, but these are not generated in all 
of the languages that Thrift supports.
+ Cassandra's client API is built entirely on top of Thrift. It should be noted 
that these documents mention default values, but these are not generated in all 
of the languages that Thrift supports.  Full examples of using Cassandra from 
Thrift, including setup boilerplate, are found on ThriftExamples.  Higher-level 
clients are linked from ClientOptions.
  
  '''WARNING:''' Some SQL/RDBMS terms are used in this documentation for 
analogy purposes. They should be thought of as just that; analogies. There are 
few similarities between how data is managed in a traditional RDBMS and 
Cassandra. Please see DataModel for more information.