db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig L Russell (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JDO-651) Modify specification to address NoSQL datastores
Date Fri, 26 Mar 2010 16:50:27 GMT

     [ https://issues.apache.org/jira/browse/JDO-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Craig L Russell reassigned JDO-651:

    Assignee: Matthew T. Adams

JDO was designed to support non-SQL datastores. In fact, the first RI was a distinctly non-SQL
implementation, essentially a key-value store. 

What needs to be done for NoSQL in general is to go through the specification in detail and
highlight those parts that cannot now be implemented reasonably by a key-value store, or a
non-transactional datastore.

NoSQL is probably too big a description of the kinds of datastores that makes sense for JDO
to support. Part of the exercise should be to categorize the NoSQL datastores to focus on
those categories that make sense for JDO.

> Modify specification to address NoSQL datastores
> ------------------------------------------------
>                 Key: JDO-651
>                 URL: https://issues.apache.org/jira/browse/JDO-651
>             Project: JDO
>          Issue Type: New Feature
>          Components: api2, specification, tck2
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
> There is increasing interest in NoSQL datastores (Google BigTable, Apache HBase, VMWare
Redis, etc), which not only do not support SQL, but also do not necessarily provide support
for traditional consistency or queriability features or guarantees, instead offering features
like eventual consistency, key-value storage mechanisms, etc.
> This request is to modify the JDO specification (and TCK & RI) so that it relaxes
certain portions of the specification, perhaps in the form of profiles similar to JavaEE 6
profiles, to allow datastores that may not support queries in general, do not support the
ACID requirements, or that support key-value-based storage mechanisms to be JDO-compliant.
 Additions to the specification may also be needed in order to directly address NoSQL-type
datastores, in a manner similar to its treatment of relational persistence mechanisms.
> Additionally, this request would serve to better support persistence on micro platforms
where consistency, queriability, etc, may not be supported.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message