[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-06-20 Thread Florian Moga (JIRA)

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

Florian Moga commented on TUSCANY-3522:
---

Patch applied at 
https://svn.apache.org/repos/asf/tuscany/collaboration/GSoC-2011-Eranda

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: HBase-API.patch, alheaders.patch, couchdb-api.path, 
> fix.patch, rest-api-1.2.patch, rest-api.patch, twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-06-18 Thread Florian Moga (JIRA)

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

Florian Moga commented on TUSCANY-3522:
---

Patch applied at 
https://svn.apache.org/repos/asf/tuscany/collaboration/GSoC-2011-Eranda/hbase/ .

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: HBase-API.patch, couchdb-api.path, fix.patch, 
> rest-api-1.2.patch, rest-api.patch, twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-06-13 Thread Florian Moga (JIRA)

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

Florian Moga commented on TUSCANY-3522:
---

Excellent! I've applied your patch in your working space.

One more thing, could you provide a build script (Maven might be most 
convenient) for the twitapp module? It would help building and importing the 
project into IDEs.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: couchdb-api.path, fix.patch, rest-api-1.2.patch, 
> rest-api.patch, twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-06-11 Thread Florian Moga (JIRA)

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

Florian Moga commented on TUSCANY-3522:
---

I've applied the couchdb-api.path at 
https://svn.apache.org/repos/asf/tuscany/collaboration/GSoC-2011-Eranda/couchdb/.

A few thoughts for future patches regarding our way of work:
1. I've noticed you started adding license headers to files, could you apply 
them to all the modules you've created?
2. We usually don't commit eclipse files (.project, .classpath, .settings) as 
they might contain absolute paths to files in your local environment and can be 
easily generated by Maven. (you might find useful to add svn ignores for them)
3. We usually don't use author/date/revision headers. SVN handles all this 
information automatically.

Otherwise, things are looking good.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: couchdb-api.path, rest-api-1.2.patch, rest-api.patch, 
> twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-06-01 Thread ant elder (JIRA)

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

ant elder commented on TUSCANY-3522:


I've applied the rest-api-1.2.patch at 
https://svn.apache.org/repos/asf/tuscany/collaboration/GSoC-2011-Eranda/cassandra.
 Sorry it took so long to get applied.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: rest-api-1.2.patch, rest-api.patch, twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-05-18 Thread Eranda Sooriyabandara (JIRA)

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

Eranda Sooriyabandara commented on TUSCANY-3522:


Hi Ant,
Thanks for creating me a work space. I'll commit all my stuff to that.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-05-17 Thread ant elder (JIRA)

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

ant elder commented on TUSCANY-3522:


Hi Eranda, I've created a folder for you in the Tuscany sandbox collaboration 
area as a place for you to put anything related to your GSoC project and I've 
committed the twitapp code there - 
https://svn.apache.org/repos/asf/tuscany/collaboration/GSoC-2011-Eranda/



> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>Assignee: Eranda Sooriyabandara
>  Labels: gsoc, gsoc2011, mentor
> Attachments: twitapp.tar.gz
>
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Re: GSoC NoSQL DataStore scenario, was: [jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-05-12 Thread Jean-Sebastien Delfino
On Wed, May 11, 2011 at 6:20 PM, Eranda Sooriyabandara
<0704...@gmail.com> wrote:
> Hi Jean-Sebastian,
> I like to try with the Twitter-like app since it will be interesting. Any
> comments?
> If you can provide me the  location of REST service example for shopping
> cart app then I can use it for get some idea from it.
> thanks
> Eranda
>

You'll find it there:
http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/applications/store/

It uses the Tuscany ATOMPub binding. ATOMPub is a good example of a
standard REST protocol.

I think there's a few more REST samples but can't find them at the
moment. Looks like most samples have been moved out of the samples
directory for some reason.

Could the guys working on REST send a few pointers to the other REST samples?

Thanks!
-- 
Jean-Sebastien


Re: GSoC NoSQL DataStore scenario, was: [jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-05-11 Thread Eranda Sooriyabandara
Hi Jean-Sebastian,
I like to try with the Twitter-like app since it will be interesting. Any
comments?
If you can provide me the  location of REST service example for shopping
cart app then I can use it for get some idea from it.
thanks
Eranda


GSoC NoSQL DataStore scenario, was: [jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-05-10 Thread Jean-Sebastien Delfino
On Sat, Apr 30, 2011 at 12:16 PM, Eranda Sooriyabandara (JIRA)
 wrote:
>
>    [ 
> https://issues.apache.org/jira/browse/TUSCANY-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027362#comment-13027362
>  ]
>
> Eranda Sooriyabandara commented on TUSCANY-3522:
> 
>
> Here are some works I did up to today,
> 1. Read about SCA
> 2. Setup and checkout some samples of some NoSQL databases,
> In here I used the hector client for Apache Cassandra and couchdb4j (use 
> JSON) client for Apache CouchDB. I think we can use some of this clients for 
> our implementations. We need to decide which one to use.
>
> There are some topics which we need to discuss about as follows,
> Sample scenario which we are going to implement over various databases. In 
> here for which extent are we going to implement the functionality?
> The REST API. We can discuss about this after finalize the scenario.
>
> After decide those we can use the database independent parts (REST API) as a 
> SCA component and mock the database access.
>

Here are a few ideas of scenarios:

a) a store with a catalog of goods, and a shopping cart app, similar
to the Tuscany store sample;

b) an app allowing you to track the location of your friends, you
build a list of friends, they update their location, and you can query
for the 5 closest ones;

c) a Twitter-like app, you follow a list of people and see the
messages they write.

These three scenarios have pretty different write / read / query
characteristics. We already have REST service examples for (a) in our
store sample. You could just build on that, but if you want more fun,
I think it'd be really interesting to try to come with REST services
for (b) or (c) as well.

Any thoughts from others in the team?
-- 
Jean-Sebastien


[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-04-30 Thread Eranda Sooriyabandara (JIRA)

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

Eranda Sooriyabandara commented on TUSCANY-3522:


Here are some works I did up to today,
1. Read about SCA 
2. Setup and checkout some samples of some NoSQL databases,
In here I used the hector client for Apache Cassandra and couchdb4j (use JSON) 
client for Apache CouchDB. I think we can use some of this clients for our 
implementations. We need to decide which one to use.

There are some topics which we need to discuss about as follows,
Sample scenario which we are going to implement over various databases. In here 
for which extent are we going to implement the functionality?
The REST API. We can discuss about this after finalize the scenario.

After decide those we can use the database independent parts (REST API) as a 
SCA component and mock the database access.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>  Labels: gsoc, gsoc2011, mentor
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-04-07 Thread kinjal brahmbhatt (JIRA)

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

kinjal brahmbhatt commented on TUSCANY-3522:


I am interested in this issue so kindly please do allow me to contribute for 
the same. Thanks.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>  Labels: gsoc, gsoc2011, mentor
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] Commented: (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase

2011-03-18 Thread Eranda Sooriyabandara (JIRA)

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

Eranda Sooriyabandara commented on TUSCANY-3522:


I am interested in this issue and l have started writing my project proposal on 
https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Develop+a+NoSQL+Datastore+component.

> [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, 
> CouchDB, Hadoop/Hbase
> -
>
> Key: TUSCANY-3522
> URL: https://issues.apache.org/jira/browse/TUSCANY-3522
> Project: Tuscany
>  Issue Type: New Feature
>Reporter: Jean-Sebastien Delfino
>  Labels: gsoc, gsoc2011, mentor
>
> NoSQL Datastore component
> =
> Write a portable data store component over a number of 'NoSQL' databases 
> (Apache Cassandra, Couchdb, Hadoop/Hbase and AppEngine Datastore databases.)
> This could be one component (written in Python or Java) or a set of 
> components (one per database) all implementing the same REST data store 
> interface, allowing applications to store data in different NoSQL databases 
> without having to worry about the details and API differences between the 
> databases.
> The project could start with just one or two databases and add more databases 
> as we go. This should be a really good opportunity for students to experiment 
> with these new NoSQL databases. 
> Resources:
> Tuscany
> http://tuscany.apache.org/
> Cassandra
> http://cassandra.apache.org/
> CouchDB
> http://couchdb.apache.org/
> Hadoop/HBase
> http://hadoop.apache.org/hbase/
> Appengine Datastore
> http://code.google.com/appengine/docs/python/datastore/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira