Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:EclipseLink/DesignDocs/362899"
(→Some additional non-relational providers to consider) |
(→Some additional non-relational providers to consider) |
||
| Line 1: | Line 1: | ||
| − | + | === Some additional non-relational providers to consider === | |
* [http://aws.amazon.com/s3 Amazon Simple Storage Service (a.k.a. S3)] | * [http://aws.amazon.com/s3 Amazon Simple Storage Service (a.k.a. S3)] | ||
* [https://github.com/xetorthio/jedis Redis (via Java client Jedis)] | * [https://github.com/xetorthio/jedis Redis (via Java client Jedis)] | ||
| − | + | === NoSQL === | |
We should consider supporting a more complex key/value structure with the Oracle NoSQL database instead of the proposed key to XML serialized Entity structure. The simple support may be sufficient for users who do not care about the structure of their data within the Oracle NoSQL database but may alienate users who want to leverage the full functionality of the database or who have a pre-existing database and non JPA NoSQL access. The Oracle NoSQL database uses a key/value structure similar to an EIS Mapped Record to store and relate data. NoSQL users are more likely to utilize the key paths and key groups to store their data than write out Java Beans to XML. | We should consider supporting a more complex key/value structure with the Oracle NoSQL database instead of the proposed key to XML serialized Entity structure. The simple support may be sufficient for users who do not care about the structure of their data within the Oracle NoSQL database but may alienate users who want to leverage the full functionality of the database or who have a pre-existing database and non JPA NoSQL access. The Oracle NoSQL database uses a key/value structure similar to an EIS Mapped Record to store and relate data. NoSQL users are more likely to utilize the key paths and key groups to store their data than write out Java Beans to XML. | ||
Latest revision as of 09:57, 22 December 2011
Some additional non-relational providers to consider
NoSQL
We should consider supporting a more complex key/value structure with the Oracle NoSQL database instead of the proposed key to XML serialized Entity structure. The simple support may be sufficient for users who do not care about the structure of their data within the Oracle NoSQL database but may alienate users who want to leverage the full functionality of the database or who have a pre-existing database and non JPA NoSQL access. The Oracle NoSQL database uses a key/value structure similar to an EIS Mapped Record to store and relate data. NoSQL users are more likely to utilize the key paths and key groups to store their data than write out Java Beans to XML.
Taking on direct support of the Oracle NoSQL database would also allow EclipseLink to manipulate the Major Key Paths storing "query indexes" that in combination with the "storeIterator()" would allow limited JPQL usage.
Gordon Yorke 20:58, 21 December 2011 (UTC)
- Not sure it says anywhere that only XML data will be supported. EIS supports mapped and indexed data as well as XML. Our NoSQL support will not be limited to XML (and will only support XML if the data source is capable of it). The current NoSQL prototype supports both XML and key/value pairs with major and minor keys. We should be able to do a findAll() query, but can't see any querying beyond that being feasible.
- James.sutherland.oracle.com 13:55, 22 December 2011 (UTC)