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

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

One further possible requirement. With a document-based store (e.g MongoDB), 
the datastore stores objects in JSON document format. With this (and with 
XML-based storage also for that matter), you have two options in terms of 
"embedding" a persistable field.
class Foo
{
    @Embedded
    Bar bar;
}

Option 1 : store the related object embedded as a document in the document of 
the owner (i.e nested)
Option 2 : map all fields of the related object to "field" names in the 
document of the owner (like we would do it for RDBMS).

Would be nice to have a meta-data way of defining these two situations 
distinctly.

> 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

        

Reply via email to