Val, I would propose adding another point to the motivations list which is related to the ORM frameworks such as Spring Data, Hibernate, Micronaut and many others.
Presently, the storage engine requires to distinguish key objects from the value ones that complicate the usage of Ignite with those ORM frameworks (especially if a key object comprises several fields). More on this can be found here: http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Key-and-Value-fields-with-same-name-and-SQL-DML-td47557.html It will be nice if the new schema-first approach allows us to work with a single entity object when it comes to the ORMs. With no need to split the entity into a key and value. Just want to be sure that the Ignite 3.0 has all the essential public APIs that would support the single-entity based approach. What do you think? - Denis On Fri, Aug 28, 2020 at 3:50 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > One of the big changes proposed for Ignite 3.0 is the so-called > "schema-first approach". To add more clarity, I've started writing the IEP > for this change: > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach > > Please take a look and let me know if there are any immediate thoughts, > suggestions, or objections. > > -Val >
