Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jnosql-dev] Early Draft review version at Jakarta NoSQL
Yes, this version we break a lot, however, we create the API, moving classes to jakarta.nosql, and moved the classes left to org.eclipse.jnosql; therefore, this version it would be impossible to do not break too much. But yes, we need to avoid to break a lot.

About GraphQL it isn't related to a NoSQL database:


On Wed, Sep 11, 2019 at 2:53 PM Werner Keil <werner.keil@xxxxxxx> wrote:

Otavio/all,

 

Thanks for the detailed outline.

I agree, the Final Release is still a good way to go, but there is no hurry given Jakarta EE 8 just went out the door last night and it isn’t even sure, if Jakarta EE 9 would allow new Features at all or it might only include refactoring from javax to jakarta packages.

 

Thus including it in the platform is a prospect at least 6-9 months or more away. So no rush to go Final with a 1.0 release of the Jakarta NoSQL spec.

 

Eclipse does not really have a term like Early Draft, as Long as a Project or spec is incubating, there can be multiple “incubating“ Releases, we aim at 0.1.0 so more incubating Releases are possible and welcome. Last but not least the whole Jakarta Development Process is also evolving and NoSQL seems in the Position as first candidate to shape and refine or improve that process as well.

 

We should try to cut changes into slightly smaller chunks, e.g. not do a PR which changes 1000 files at the same time, except Maybe significant package changes (like org.jnosql to org.eclipse, but that seems mostly done)

 

Whenever Jakarta Persistence (formerly known as JPA) is Ready and interested, we should try to see, what synergies exist regarding some common Elements like “Entity“ or others.

 

About Graph API it may not be so easy to get the very new GraphQL feature at MicroProfile to emerge into Jakarta EE, but looking at its duplication of annotations like @Query etc. it feels there could be benefit if a common GraphQL module similar to the “JPA Light” idea was also possible there ;-)

 

Regards,

Werner

 

Sent from Mail for Windows 10

 

From: Otavio Santana
Sent: Wednesday, September 11, 2019 13:57
To: jnosql developer discussions; nosql developer discussions
Subject: [jnosql-dev] Early Draft review version at Jakarta NoSQL

 

Hey everyone, I would like to hear your option about release a new version of Eclipse JNoSQL, this time as Jakarta NoSQL.

Releases:

  • Split the API from the Implementation
  • Move the API to Jakarta NoSQL project
  • Update the project using Jakarta NoSQL
  • Add support to Apache Solr
  • Update the group id to org.eclipse.jnosql
  • Update query to key-value
  • Sync method nomenclature
  • Support to Iterable
  • Make all return be a Stream
  • Fixes order in Graph API


IMHO: The API is not ready to a final version that still several things to do such as TCK and standardize Graph API, however, what we have is a minimum viable product, MVP,  to receive more feedback from the Java Community.

In the JCP we have an Early Draft review version, I would like to do something similar at Jakarta NoSQL.

Thoughts?

 

--

Otávio Santana

 

 

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jnosql-dev


--
Otávio Santana

Back to the top