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 Tue, 11 Mar 2014 19:48:42 GMT

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

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

Further update to the spec required for datastores that don't support transactions (Cassandra
for example). Clearly an implementation can wire tx.begin/tx.commit/tx.rollback to be no-op,
so the user who switches to a non-transactional datastore can use their same persistence code.
The spec would need to consider lifecycle transitions for such a datastore - supporting PCLEAN->HOLLOW
on commit makes sense, but would also need to document that rollback operations would be the
same as commit.

Would likely be good to add an optional feature in to 11.6
javax.jdo.option.Transactions

Maybe there are other places that this impacts on.

> 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 (3.0)
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>              Labels: jdo, nosql, profile, specification
>             Fix For: JDO 3 maintenance release 2 (3.2)
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message