Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
> @Chetan: why would the configs not be stored in the repo? I do not see how > this relates to non-OSGi environments Well thats the basic config required to configure DocumentNodeStore/SegmentNodeStore. These config cannot be stored as content. Other settings like security related config currently is not read from NodeStore and in OSGi env is being provided by OSGi ConfigAdmin. And more other settings like Index are currently stored as content Chetan Mehrotra On Wed, Apr 2, 2014 at 3:49 PM, Michael Marth wrote: > > On 02 Apr 2014, at 08:06, Jukka Zitting > mailto:jukka.zitt...@gmail.com>> wrote: > > That design gets broken if components > start storing data separately in the repository folder. > > Agree with that design principle, but the (shared) file system DS is a valid > exception IMO (same for the S3 DS). > > Later we would probably store the config files when using Oak outside > of std OSGi env like with PojoSR > > @Chetan: why would the configs not be stored in the repo? I do not see how > this relates to non-OSGi environments
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
On 02 Apr 2014, at 08:06, Jukka Zitting mailto:jukka.zitt...@gmail.com>> wrote: That design gets broken if components start storing data separately in the repository folder. Agree with that design principle, but the (shared) file system DS is a valid exception IMO (same for the S3 DS). Later we would probably store the config files when using Oak outside of std OSGi env like with PojoSR @Chetan: why would the configs not be stored in the repo? I do not see how this relates to non-OSGi environments
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
On 02/04/2014 07:48, Chetan Mehrotra wrote: > On Wed, Apr 2, 2014 at 11:36 AM, Jukka Zitting > wrote: >> I consider this an unfortunate recent development. > Not sure. There are some deployment scenarios where a shared > FileDataStore is a must requirement and thus we need to support cases > where blobs can be stored separately from node data. Yes it adds to > the complexity of backup but then such a feature is required then that > cost has to be paid. I back this. Sharing immutable blobs between instances is a must have for big repositories. I know that with mongo you can shard etc, but still you're duplicating the space (other that there are functionalities that address this in mongo). Backup will have to be arranged separately with something like rsync or netapp snapshots, etc. D.
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
On 2.4.14 8:06 , Jukka Zitting wrote: Hi, On Mon, Mar 31, 2014 at 11:59 PM, Chetan Mehrotra wrote: Why the . extra subdirectory? The repository home folder is used by various components in Oak. I consider this an unfortunate recent development. Most parts in Oak have explicitly been designed to store all content and configuration within the NodeStore/MicroKernel, which is why we're able to localize all clustering, backup and other such concerns within those backend implementations. That design gets broken if components start storing data separately in the repository folder. I double that. Everything is content was and IMO should still be a key driver for the design. Michael BR, Jukka Zitting
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
On Wed, Apr 2, 2014 at 11:36 AM, Jukka Zitting wrote: > I consider this an unfortunate recent development. Not sure. There are some deployment scenarios where a shared FileDataStore is a must requirement and thus we need to support cases where blobs can be stored separately from node data. Yes it adds to the complexity of backup but then such a feature is required then that cost has to be paid. Default setups currently do not use FileDataStore or BlobStore with SegmentNodeStore. So as per defaults original design is still honored. Chetan Mehrotra
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
Hi, On Mon, Mar 31, 2014 at 11:59 PM, Chetan Mehrotra wrote: >> Why the . extra subdirectory? > > The repository home folder is used by various components in Oak. I consider this an unfortunate recent development. Most parts in Oak have explicitly been designed to store all content and configuration within the NodeStore/MicroKernel, which is why we're able to localize all clustering, backup and other such concerns within those backend implementations. That design gets broken if components start storing data separately in the repository folder. BR, Jukka Zitting
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
> Why the . extra subdirectory? The repository home folder is used by various components in Oak. For example FileDataStore stores the binaries under /datastore folder. Hence the subdirectory. So it would result in /segmentstore /datastore Later we would probably store the config files when using Oak outside of std OSGi env like with PojoSR Chetan Mehrotra On Mon, Mar 31, 2014 at 9:50 PM, Jukka Zitting wrote: > Hi, > > On Fri, Mar 14, 2014 at 4:42 AM, wrote: >> @@ -84,6 +112,8 @@ public class SegmentNodeStoreService ext >> String directory = lookup(context, DIRECTORY); >> if (directory == null) { >> directory = "tarmk"; >> +}else{ >> +directory = FilenameUtils.concat(directory, "segmentstore"); >> } > > Why the extra subdirectory? > > BR, > > Jukka Zitting
Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/ja
Hi, On Fri, Mar 14, 2014 at 4:42 AM, wrote: > @@ -84,6 +112,8 @@ public class SegmentNodeStoreService ext > String directory = lookup(context, DIRECTORY); > if (directory == null) { > directory = "tarmk"; > +}else{ > +directory = FilenameUtils.concat(directory, "segmentstore"); > } Why the extra subdirectory? BR, Jukka Zitting