cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian ONeill (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3380) REST Layer
Date Thu, 20 Oct 2011 13:16:10 GMT


Brian ONeill commented on CASSANDRA-3380:


I hadn't looked at Riak much until you sent that link out last night.  Looking at what they
provide over HTTP, it is a pretty powerful, especially around the Map/Reduce capabilities:

Maybe there is an opportunity here to deliver the same kinds of capabilities on top of Cassandra?
It would be really slick if we could sling a PIG script at a URL and have it result in new
column families or updated data in Cassandra.

If we were looking to get rid of the contrib directory, maybe we carve off rest+pig+hadoop
capabilities into its own project.  That project would provide services on top of Cassandra
exposed via REST.  (again.. very similar to what SOLR provided for Lucene for a long time,
until they merged)
> REST Layer 
> -----------
>                 Key: CASSANDRA-3380
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>         Environment: Unix / Max OS X
>            Reporter: Brian ONeill
>         Attachments: trunk-3380.txt
> This is a native rest layer for Cassandra implementing AbstractCassandraDaemon.
> It uses JAX-RS fueled by Apache CXF.
> Presently it supports the following operations JSON over HTTP:
>  - Create keyspace
>  - Drop keyspace
>  - Create column family
>  - Drop column family
>  - Insert row
>  - Fetch row
>  - Delete row
>  - Insert column
>  - Delete column 
>  - Fetch column
> The patch creates a new project in contrib/rest.  You can compile the project using "ant",
which uses ivy to pull in dependencies.  To get setup, you can also use the pom.xml file and
m2eclipse to get it into Eclipse.
> Once compiled, simpy run "bin/rest_cassandra" and follow along in the README.txt

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message