Sounds like a good plan, it always worked well for me to have
prototypes working first and then come the the Infinispan mailing list
with a concrete proposal.
+10 for the better conditional API.. I've always struggled with that,
you can find some references to the discussion by searching for "MVCC
Right now I want to do that purely in Hibernate integration part, as I
don't see why such user approach should not work - replacing remove(key)
calls with put(key, tombstone singleton, expiration args). It's possible
that I hit the wall somewhere and have to go down to Infinispan.
My general pl
Great, I also thought tombstones would be essential to improve the
2lc. Are you going to bake that feature within Infinispan or as a
customization within the Hibernate code?
On 17 August 2015 at 08:26, Radim Vansa wrote:
> OK, thanks for the info. I am truly trying to rewrite the refactor the
> t
OK, thanks for the info. I am truly trying to rewrite the refactor the
testsuite as part of [1] so that we can run the tests against all
concurrency strategy modes and cache configurations (I am working on
tombstone-based 2LC implementation). Also, I hope I can speed up the
testsuite (I see tha
Context is this IRC question:
[08:14:33] sannegrinovero: Hi, may I ask why have you
sometimes added InfinispanTestingSetup as @ClassRule and sometimes as
@Rule in HHH-10001?
[11:06] [08:14:34] jira [HHH-10001] Make the testsuite
compatible with Infinispan 8 [Closed (Fixed) Task, Major, Sanne
Gri
