+1 for initializing the default config unconditionally Regards Julian
On Fri, Oct 21, 2016 at 12:14 PM, Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: > Opened OAK-4975 for query around default config handling. > Chetan Mehrotra > > > On Fri, Oct 21, 2016 at 2:14 PM, Davide Giannella <dav...@apache.org> wrote: >> On 21/10/2016 08:23, Michael Marth wrote: >>> Hi Chetan, >>> >>> Re “Should we ship with a default config”: >>> >>> I vote for a small default config: >>> - default because: if the feature is always-on in trunk we will get better >>> insights in day-to-day work (as opposed to switching it on only >>> occasionally) >>> - small because: the optimal bundling is probably very specific to the >>> application and its read-write patterns. Your suggestion to include nt:file >>> (and maybe rep:AccessControllable) looks reasonable to me, though. >>> >> +1 but I would not do it that DocumentNS has to actively register it. I >> would have a plain RepositoryInitialiser always on beside the >> InitialContent. So that it's clear it's somewhat different. In the end >> as far as I understood it doesn't matter if we're running segment, tar >> or Document. The config will affect only Document. >> >> Davide >> >>
