Looks like you are using the default MongoBlobStore. Based on that
1) Based on what size data goes in blob collection
For MongoBlobStore that is determined via
org.apache.jackrabbit.oak.spi.blob.AbstractBlobStore#blockSizeMin
which defaults to 4096
2) Is there any reference between Nodes and
Hi Lukas,
thanks for your feedback. changing the default to 127.0.0.1 makes
sense. I’ll create an issue and change oak-run accordingly.
Regards
Marcel
On 25/06/14 21:22, Lukas Kahwe Smith sm...@pooteeweet.org wrote:
On 25 Jun 2014, at 13:25, Lukas Kahwe Smith sm...@pooteeweet.org wrote:
hi jukka
this is not quite true. as i will explain below.
first i would strongly recommend not to rely on the current implementation.
if we have the requirement to evaluated permissions based on the path
we may extend the permissionprovider which IMO is the key API for these
cases; not the
On 26 Jun 2014, at 09:46, Marcel Reutegger mreut...@adobe.com wrote:
Hi Lukas,
thanks for your feedback. changing the default to 127.0.0.1 makes
sense. I’ll create an issue and change oak-run accordingly.
great!
updated to 1.0.1 and all seems to work nicely (needed to update MongoDB to
Thanks Chetan, for the helpful info.
Yes you are correct I am talking about MongoBlobStore here.
I tried to find out the reference by using following query
db.nodes.find({blobId:{$exists:true}}. It returns nothing. Can you please
point me to the query I need to use to see the reference at work
Hi,
I tried to backup a segmentstore using
java -mx2g -jar oak-run-1.0.2-SNAPSHOT.jar backup segmentstore s2
java.lang.OutOfMemoryError: Java heap space
I think 2 GB heap are quite a lot, is this expected? The repository is
relatively large (2260 tar files; 566 GB). So anyway, then I tried with
Hi,
Can't we do the ACL check lazily?
That's what we do right now.
Regards,
Thomas
Hi,
On Thu, Jun 26, 2014 at 4:10 AM, Angela Schreiber anch...@adobe.com wrote:
however, please be aware that one key feature of oak (compared to
jackrabbit which only allowed permission evaluation by path) is that
it always needs to be clear if the target for the permission evaluation
is a
Hi,
On Thu, Jun 26, 2014 at 2:55 AM, Davide Giannella dav...@apache.org wrote:
Can't we do the ACL check lazily? Instead of the query engine looping
through the nodes and check, if there's no need of doing so already (IE
sorting), why not returning the set and then filter out the ACLs while
Hi,
On Thu, Jun 26, 2014 at 9:05 AM, Thomas Mueller muel...@adobe.com wrote:
I tried to backup a segmentstore using
java -mx2g -jar oak-run-1.0.2-SNAPSHOT.jar backup segmentstore s2
java.lang.OutOfMemoryError: Java heap space
I think 2 GB heap are quite a lot, is this expected? The
Hi,
OK, makes sense. I'll create a Jira issue for the external blob case,
and will find out more about the memory issue.
Regards,
Thomas
On 26/06/14 15:55, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
On Thu, Jun 26, 2014 at 9:05 AM, Thomas Mueller muel...@adobe.com wrote:
I tried to
Created OAK-1921
On 26/06/14 15:58, Thomas Mueller muel...@adobe.com wrote:
Hi,
OK, makes sense. I'll create a Jira issue for the external blob case,
and will find out more about the memory issue.
Regards,
Thomas
On 26/06/14 15:55, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
On Thu,
Hi,
On Wed, Jun 25, 2014 at 10:12 AM, Davide Giannella dav...@apache.org wrote:
Any thoughts on the above?
I generally agree, as my thinking in the original thread was to have a
unified interface where (im)mutability was just an aspect of specific
instances/implementations.
On the other hand
13 matches
Mail list logo
