Hi,
afaik with Oak the too many child nodes problem of JR2 is solved, therefore
I'm wondering what the best way to store a queue in the repository is?
In my use cases, there are usually not many items within a single queue,
let's say a few hundreds. In some cases the queue might grow to some
Today I run the same scenario, but couldn't reproduce the issue.
I will try to isolate this further, and will reply with more data.
Thanks
Himanshu
On Mon, Jul 28, 2014 at 1:58 PM, Michael Dürig mdue...@apache.org wrote:
On 28.7.14 9:56 , Vikas Saurabh wrote:
By Java API, I assume you
Hi,
I can totally see that it might be useful to be able to go through the Oak/JCR
API to have a queue but maybe this is stretching Oak a bit far if you end up
with 1k+ queues.
However I think it would be great to look more into federation for this. I
think ModeShape supports this quite well
Hi,
I noticed that even if the h2 dependency is now included with a 'test'
scope [0], we still embed it in the jar file [1], is there a need to still
do this or was it simply forgotten?
thanks,
alex
[0]
https://github.com/apache/jackrabbit-oak/commit/74cbf1ffb40b452195e944704ecb8a63ab273c80
Using a different storage than JCR would be easy in my case, however I
*want* to use JCR
Carsten
2014-07-30 14:55 GMT+02:00 Lukas Smith sm...@pooteeweet.org:
Hi,
I can totally see that it might be useful to be able to go through the
Oak/JCR API to have a queue but maybe this is stretching
This is being tracked via OAK-1708. Julian do we still require it or
these can be removed now?
Chetan Mehrotra
On Wed, Jul 30, 2014 at 6:41 PM, Alex Parvulescu
alex.parvule...@gmail.com wrote:
Hi,
I noticed that even if the h2 dependency is now included with a 'test'
scope [0], we still
