Re: [hibernate-dev] [hibernate-announce] Releasing Hibernate OGM 5.1.0.Beta1: now with Hot Rod support!

I understand that you don't want to scare users off, but I would mention that at least in the section about deciding between embedded and Hot Rod: "When connecting to an /Infinispan Server/ over the /Hot Rod client/, the architecture is similar to having Hibernate connect to traditional database: the data is stored on the /Infinispan Server/ nodes, and Hibernate OGM uses a client with a pool of TCP connections to talk to the server." Traditional databases are transactional, so I would put a notice about no-transactions here, with a link to "9.3.4. Storage Principles of the Infinispan Remote dataprovider" Most people probably understand what *is* the loss of referential integrity, but 9.3.4 is not really specific *when* does this happen. As you speak about "interrupting Hibernate OGM", I would assume that this is limited to a case when some operation fails (due to network breakage), but it's not clear that this can happen even with successful concurrent operations. Therefore, an example that can lead to broken integrity could be useful, along with information about concurrent operations that are safe (basically saying that if each session uses distinct set of entities, you are safe).

Is there any option to detect (and fix) the problems? (by a batch job...?)

Radim On 11/08/2016 01:53 PM, Sanne Grinovero wrote: > > Thanks Radim! > > the blog attempts to be short, I mention the Referential Integrity > problem in the reference documentation: > > " > Referential integrity > While we can use relations based on foreign keys, Infinispan has no > notion of referential integrity. Hibernate is able to maintain the > integrity as it won’t "forget" stale references, > but since the > storage doesn’t support transactions either it is possible to > interrupt Hibernate OGM during such maintenance and introduce breaks > of integrity. > " > - > https://docs.jboss.org/hibernate/ogm/5.1/reference/en-US/html_single/#sto... > > It's not explicitly listed in the known limitations, as I consider it > part of the "there's no transactions" point here: > - > https://docs.jboss.org/hibernate/ogm/5.1/reference/en-US/html_single/#kno... > > You think that's enough? It's a though one, as I want to be clear > about the limitations but w/o scaring people off by repeating > limitations too many times. > There are also various big highlighted baloons mentioning: > > " > Caution > The Hibernate OGM support for Infinispan Remote is considered > experimental. " > > Happy to clarify the docs as needed. > > Thanks! > Sanne > > > On 8 November 2016 at 17:50, Radim Vansa <rvansa(a)redhat.com&gt; wrote: >> >> Wouldn't it be worth mentioning the lack of referential integrity among >> the limitations? >> >> Anyway, thumbs up! >> >> Radim >> >> On 11/08/2016 12:16 PM, Sanne Grinovero wrote: >>> >>> Hello everyone, >>> >>> we can finally announce that Hibernate OGM 5.1.0.Beta1 is released, >>> and now includes support for Infinispan Server, alias Hot Rod, also >>> known as Infinispan Remote .. >>> >>> - http://in.relation.to/2016/11/08/hibernate-ogm-with-hotrod-support >>> >>> We also released Hibernate OGM 5.0.3.Final >>> >>> Kind Regards, >>> Sanne >>> _______________________________________________ >>> hibernate-dev mailing list >>> hibernate-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> >> >> -- >> Radim Vansa <rvansa(a)redhat.com&gt; >> JBoss Performance Team >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Radim Vansa <rvansa(a)redhat.com&gt; JBoss Performance Team