I'm Fabio, nice to meet you.
Speaking of the current implementation of the Infinispan remote dialect of
Hibernate OGM, working on issue OGM-1206 and talking with Davide I noticed
that the unit of work commands are executed (flushed to datastore) at the
end of the transaction itself.
In particular I noticed that the commands are stored in a transaction
scoped object of type org.hibernate.ogm.dialect.batch.spi.OperationsQueue.
Instead of perfom one remote invocation for each command in the method
maybe we could invoke a proper Infispan Remote Server Task to execute the
command queue on server side as a bulk operation.
Moving the execution of the server-side command list (Infinispan) we would
have the advantage of reducing remote interactions. Moreover and above all
the execution of the command queue would be a transactional work unit, on
which could be apply a Repeteable Read isolation level, for instance.
The solution would not solve the need for an XA client instead, but it
could be adopted by customers interested in local transactions.
What do you think about it?
Can I open a Jira issue?
FABIO MASSIMO ERCOLI
Senior Software Engineer - Hibernate & Data Platform
Red Hat <https://www.redhat.com/>
fabio.ercoli(a)redhat.com M: (+39)-329.8681441
Now that I've moved ORM publishing to Bintray some of the layout of
hibernate.org in regards to releases is not-so-nice. Most of this comes
into play in the `project-releases-series.html.haml` file use as the layout
for these "series" pages.
1. Some of the text injected is just wrong. "Maven artifacts of
Hibernate ORM are published to Maven Central and to the JBoss Maven
Repository. Refer to the Maven Getting Started guide on the Jboss Wiki for
more information on how to configure Maven." Most of that is now
2. One of the niceties of moving to Bintray is having a singular URL to
refer to the artifacts included in the release. E.g.
layout here though is set up to list out each artifact individually.
I'd like to change this for ORM 5.3 moving forward such that the "Maven,
Gradle..." section simply points to the Bintray URL, as well as changing
that text to be ore accurate. Is this going to be as simple as adding a
new layout (`project-releases-series-bintray.html.haml`?) and using that as
the layout for http://hibernate.org/orm/releases/5.3/ ?
Wanted to remind everyone that tomorrow is the next time-boxed release for
I wanted to get everyone's opinions about the version number, whether this
should be Beta2 or CR1. IMO It depends how you view the remaining
challenges with the JPA TCK, with CR1 being the optimistic view.
Just so you know, I just made a few minor changes to the website:
- in the Releases dymanic submenu, you now have a label stating "latest
stable"/"development" to make it clearer what the versions are (it's
especially useful at this point of the ORM development for instance as 5.3
is the latest but not yet considered stable)
- I made the Documentation entry menu of ORM dynamic with a submenu
following the same principles as for Releases. It avoids going to the
latest then using the dropdown at the top (I kept the dropdown anyway)
In passing, I also added a placeholder page for the ORM 5.3 doc stating it
will be available soon.