db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-651) Modify specification to address NoSQL datastores
Date Mon, 31 Jan 2011 10:33:11 GMT

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

Andy Jefferson commented on JDO-651:
------------------------------------

DataNucleus support on HBase hasn't encountered anything that cannot fit into the JDO spec.
http://www.datanucleus.org/products/accessplatform_3_0/datastore_features.html

Initial work supporting MongoDB likewise hasn't had such problems.

The only thing I vaguely remember was when a DN user was implementing support for Cassandra
it would have been convenient to have a way of setting properties on the PM (as opposed to
the PMF). This would add extra flexibility anyway, allowing vendor-specifics to be turned
on/off during a transaction for example.

> 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: api, specification, tck
>    Affects Versions: JDO 3
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>              Labels: jdo, nosql, profile, specification
>             Fix For: JDO 3 maintenance release 1
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message