Hi, A small update about the 2.4.2 release. Unfortunately I found yet another bug which causes data inconsistencies. This time it's related to the handling of node.refresh(). I do have a concurrent stress test which can consistently reproduce this, but not a clear reproduction path yet. Since we are in the process of chasing down this bug I want to hold of the 2.4.2 release for a little bit longer so we hopefully have a fix for this issue in the release. I will open a jira issue so other people can have a look as well.
Regards, Bart On Mon, Apr 30, 2012 at 10:21 AM, David Buchmann <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi, > > it would be great to have https://issues.apache.org/jira/browse/JCR-3245 > in 2.4 at some point. > > at this point the patch will not help jackrabbit being faster but is > meant for our php client jackalope. of course other remoting clients > like the jackrabbit spi2dav could start using the feature as well to > save some roundtrips. > > cheers,david > > Am 20.04.2012 12:29, schrieb Jukka Zitting: >> Hi, >> >> On Fri, Apr 20, 2012 at 12:26 PM, Torgeir Veimo <[email protected]> >> wrote: >>> Any hope to get https://issues.apache.org/jira/browse/JCR-3242 >>> (upgrade to Lucene 3.5/3.6) in this release? >> >> That's a pretty major change to include in a patch release. I'd rather >> ship an unstable 2.5.0 release from trunk once JCR-3242 is ready. >> >> BR, >> >> Jukka Zitting > > - -- > Liip AG // Agile Web Development // T +41 26 422 25 11 > CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk+eS3cACgkQqBnXnqWBgIsyUwCfc/ulcpUOtzlWEPpX2ws+tG0s > jNUAn1v0QSSvH/DNkkYsAxI4YlXnV1BJ > =Zp7P > -----END PGP SIGNATURE-----
