You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Sumedha Kodithuwakku (Commented) (JIRA)" <ji...@apache.org> on 2012/03/31 09:11:14 UTC
[jira] [Commented] (AIRAVATA-341) [GSOC] NoSQL implementation for
Airavata Registry
[ https://issues.apache.org/jira/browse/AIRAVATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243064#comment-13243064 ]
Sumedha Kodithuwakku commented on AIRAVATA-341:
-----------------------------------------------
I did some background studies on Airavata and also went through the registry API and the AiravataClient roughly as suggested by Marlon in dev-list. So I have few things to clarify about implementation of this new feature.
As I understood Apache Jackrabbit is used as the content repository and it is accessed via the JCR API. As per the discussion with Marlon, the main goal of this project is to replace the storing mechanism with a NoSQL solution. I'm not clear whether the project is to replace the whole Jackrabbit implementation with a NoSQL based implementation which can be accessed through the JCR API or to implement a NoSQL storage mechanism replacing the current storage mechanism inside Jackrabbit. Please can someone clarify on this.
Also It would be appreciated if I can know some more details on what will be expected from the project and the initial requirements.
> [GSOC] NoSQL implementation for Airavata Registry
> -------------------------------------------------
>
> Key: AIRAVATA-341
> URL: https://issues.apache.org/jira/browse/AIRAVATA-341
> Project: Airavata
> Issue Type: New Feature
> Reporter: Marlon Pierce
> Assignee: Marlon Pierce
> Priority: Minor
> Labels: gsoc, gsoc2012, mentor
>
> Airavata's Registry is used to store and retrieve services and workflows. The Registry is currently very lightweight with an implementation based on Apache Jackrabbit. This task is to develop a more powerful registry capable of handling a wider variety of use cases and science gateway metadata. Issues include development of JSON metadata models for different use cases, development and evaluation of metadata search capabilities (both expressiveness and performance), and development and evaluation of access policies for the metadata. The latter may involve integration with Apache Rave as an OpenSocial engine for defining groups and filtering requests.
> Evaluating the capabilities of multiple NoSQL databases will be an important component of this task. Candidate technologies from Apache include Cassandra and CouchDB, but appropriately licensed non-Apache projects such as MongoDB will also be evaluated.
> Sample use case scenarios will include computational chemistry, material science, astronomy, and earth science.
>
--
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