cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Update of "CLI Design" by wolfeidau
Date Sat, 20 Feb 2010 23:27:02 GMT
Dear Wiki user,

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

The "CLI Design" page has been changed by wolfeidau.
http://wiki.apache.org/cassandra/CLI%20Design?action=diff&rev1=7&rev2=8

--------------------------------------------------

  
   * Modeling data in Cassandra is very different from the typical RDBMS, which people are
used to using.
   * The tools provided need some work to address error management and overall ease of use.
-  * Most of the interest comes from segments of the php, Python and Ruby communities which
are not entirely familiar with the Java Language(for example using timeuuid in php), and how
to manage java based services.
+  * Most of the interest comes from segments of the PHP, Python and Ruby communities which
are not entirely familiar with the Java Language(for example using timeuuid in php), and how
to manage java based services.
   * Monitoring of statistics requires an understanding of JMX and is difficult to do outside
of the Java Virtual Machine.
   * The API through which Cassandra is accessed can be difficult to build, quite brittle
at times.
  
@@ -18, +18 @@

  
  In the following sections each of the previously mentioned reasons will be explored in more
detail and some ideas outlined to solve them.
  
+ == Data Modelling ==
+ 
+  * Need some more sample data models built up and bundled with Cassandra
+  * It would be handy to have some sort of visualisation to graphically illustrate the structure
of the CF(s)
+ 
+ == Tools ==
+ 
+  * Single interface to the Cassandra database, which is in itself an interesting problem
as it is distributed.
+  ** Should be able to access statistics, 
+  ** modify and query data. 
+  ** Generate reports in various ouput formats, json, xml ect.
+ 
+ == Improve access from other Languages ==
+ 
+  * More examples with a focus on illustrating common anti patterns normally experienced
when accessing Cassandra from that language.
+  * More documentation
+ 
+ == Management ==
+ 
+  * Get some basic summary report interface which just pulls out all the important stuff
which people from other languages may not be aware of. Use colors to indicate areas which
need attention.
+  * More documentation about how to see what is going on inside the JVM, and Cassandra
+ 
+ == API Improvements ==
+ 
+ * Improve or replace the current API interface with a focus on better error handling and
messages
+ * More documentation
+ 

Mime
View raw message