Would this be an appropriate template for how to create the FileStore with
a FileDataStore BlobStore?  (Am I getting the relationship right there?):

https://gist.github.com/chetanmeh/6242d0a7fe421955d456

Thanks, - Bill

On Wed, Mar 21, 2018 at 11:48 AM, William Markmann <
b...@counterpointconsulting.com> wrote:

> Understand reasoning behind the first point, just wanted to check if I'd
> missed some.
>
> Your second point is more interesting to me, though...  what you're
> suggesting sounds like I'm putting the JCR "tree" and the file content in
> the same tar files when I don't have to?  I assumed they were part and
> parcel... :-)
>
> The completely stripped down configuration I do to get a repository
> instance the rest of my application uses looks like:
>
> FileStoreBuilder fsBuilder = FileStoreBuilder.fileStoreBuilder(new
> File(repoDirectory));
> this.fs = fsBuilder.build();
>
> SegmentNodeStoreBuilder nsBuilder = SegmentNodeStoreBuilders.builder(fs);
> this.ns = nsBuilder.build();
> this.executor = Oak.defaultExecutorService();
> this.oak = new Oak(ns);
> this.jcr = new Jcr(oak);
> this.repository = jcr.createRepository();
>
> ....and that's it.  How would I tell it to split out the binary data?  The
> NodeStore documentation says "By default SegmentNodeStore (aka TarMK)
> does not require a BlobStore. Instead the binary content is directly stored
> as part of segment blob itself...  FileDataStore - This should be used if
> the blobs/binaries have to be shared between multiple repositories."
>
> Should I be using the FileDataStore even though I'm not sharing them
> between repositories?  Would this be a general guideline for using the
> SegmentNodeStore with a large volume of data?
>
> Thanks! - Bill
>
>
> On Wed, Mar 21, 2018 at 9:02 AM, Marcel Reutegger <
> mreut...@adobe.com.invalid> wrote:
>
>> Hi,
>>
>> On 17.03.18 18:32, William Markmann wrote:
>>
>>> 1) Is it necessary to do the above in two steps, or can a Node be created
>>> and checked in with the VersionManager in one shot?
>>>
>>
>> Yes, this is necessary. The JCR specification defines a checkin as a
>> workspace operation, which can only operate on saved changes. That is, you
>> must first save the node and only then you can check it in.
>>
>> 4) Is there anything inherent in the SegmentNodeStore that would decrease
>>> in performance as the repository grows?
>>>
>>
>> I'm not exactly sure how your deployment looks like, but you may be
>> storing the binary data in the tar files written by the SegmentNodeStore as
>> well. This has an adverse effect on data locality and the general
>> recommendation is to configure a separate DataStore for binary data.
>>
>> Regards
>>  Marcel
>>
>
>
>
> --
> *Bill Markmann*
> *President | 866 809 0394 x 701*
> *Counterpoint Consulting*
> *Automate. Innovate. Accelerate.*
> c20g.com | *Blog <http://www.c20g.com/site/blog> **| Linkedin
> <http://www.linkedin.com/company/counterpoint-consulting-inc.>** |
> Twitter <https://twitter.com/c20g>*
>



-- 
*Bill Markmann*
*President | 866 809 0394 x 701*
*Counterpoint Consulting*
*Automate. Innovate. Accelerate.*
c20g.com | *Blog <http://www.c20g.com/site/blog> **| Linkedin
<http://www.linkedin.com/company/counterpoint-consulting-inc.>** | Twitter
<https://twitter.com/c20g>*

Reply via email to