eclipse-ee4j
Inclusion of Jakarta NoSQL in Jakarta EE 11?
Use this issue to discuss whether Jakarta NoSQL is a candidate for inclusion in Jakarta EE 11.
Red Hat will oppose this for at least two reasons. 1. we don't have users asking for this. To be part of a platform or profile there needs to be demonstrated user demand. 2. The current approach is introducing a new query language to try to abstract across implementations. This is not what users currently do, and results in a weaker feature. We looked at using the JPA API and JPQL in our https://hibernate.org/ogm/ approach in addition to exposing the native query capabilities.
Hibernate OGM is not maintained anymore.
@starksm64 Why are you opposing something new that's maintained? There is no new query language in Jakarta NoSQL, aside from the ability to use those of a particular NoSQL DB like
- CQL (Cassandra)
- Cypher (Neo4J)
- etc.
Think of Native Queries in JPA.
It seams reasonable for NoSQL to wait for Jakarta Data due to upstream dependencies, potentially data, although depending on what's otherwise decided between Jakarta EE and MicroProfile, MP Config may be a viable alternative, especially for the compatible implementation JNoSQL.
I think NoSQL is a perfect candidate. It will bring a rich abstracted API (KeyValue, Document, Column, Graph) over NoSQL databases.
