[ https://issues.apache.org/jira/browse/JDO-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Jefferson updated JDO-651: ------------------------------- Fix Version/s: (was: JDO 3.2) No clear definition of work required, hence cannot be considered for "next release" until there is > 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 > > 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.3.4#6332)