The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.6.0. The release is available for download at:
http://jackrabbit.apache.org/downloads.html
See the full release notes below for details about this release.
Release Notes -- Apache Jackrabbit --
Dear Jackrabbit Dev Team,
My name is Lakshitha de Silva and I am a PhD student at University of St
Andrews, UK. My research is focused on checking architectural conformance
in Java program at runtime. I am hoping to use Jackrabbit as an evaluation
candidate for my research as it appears to have a
Hi,
I'm a bit skeptical if the added complexity is worth the disk space
saving.
As for disk space: when storing data as JSON (as I guess 99% of all users
of MongoDB do), MongoDB compresses the data as well. Currently the format
seems to be BSON, and there are plans to Snappy / LZO / LZ4. See
Hi,
On Thu, Feb 14, 2013 at 10:52 AM, Thomas Mueller muel...@adobe.com wrote:
So I guess disk space and memory usage is just different, but it's not
so easy to say whether it's better or worse.
Indeed. Ultimately we'll need higher-level performance benchmarks to
properly evaluate these things.
hi guys,
I'm wondering if we could promote the #setHook method to the NodeStore api?
CommitHooks are an important part of Oak and all the existing
implementations have one anyway.
thanks,
alex
Hi,
On Thu, Feb 14, 2013 at 1:13 PM, Alex Parvulescu
alex.parvule...@gmail.com wrote:
I'm wondering if we could promote the #setHook method to the NodeStore api?
The intention so far has been to keep NodeStore functionally
equivalent to the MicroKernel, i.e. just a higher-level wrapper that
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/1573
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
hi
I'm wondering if we could promote the #setHook method to the NodeStore api?
The intention so far has been to keep NodeStore functionally
equivalent to the MicroKernel, i.e. just a higher-level wrapper that
hides details like caching, JSOP processing and revision/path
tracking. Adding
see https://issues.apache.org/jira/browse/OAK-627
On 2/14/13 6:38 PM, Angela Schreiber wrote:
hi
I'm wondering if we could promote the #setHook method to the NodeStore api?
The intention so far has been to keep NodeStore functionally
equivalent to the MicroKernel, i.e. just a higher-level
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/1578
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
On 14.2.13 16:06, thom...@apache.org wrote:
-@Ignore
public void batchInsert() throws Exception {
I reverted this part since it broke the build.
Michael
Hi,
AFAIK indexing currently uses commit hooks for keeping the index up to
date when content changes. As Jukka mentioned this might not be the
right thing to do since when a commit fails, we end up with invalid
index entries. The conclusion was, that indexing should use the
Observer, which
On Feb 14, 2013, at 8:27 , Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
When discussing workspaces and our options for implementing them, our
main options so far have been:
1) No workspace support (with jcr:system just a normal subtree)
2) Workspaces as fully independent trees (each
13 matches
Mail list logo