[JDO-651] Modify specification to address NoSQL datastores

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: JDO 3 (3.0)
• Component/s: api, specification, tck
• Labels: jdo nosql profile specification
• Assignee: Matthew T. Adams
• Reporter: Matthew T. Adams
• Created: 25/Mar/10 17:27
• Updated: 31/May/15 18:28

Description

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.

Issue Links

• relates to: JDO-589 Allow makePersistent and deletePersistent outside a transaction