[jira] [Commented] (OAK-6312) Unify NodeStore/DataStore configurations

["Arek Kita (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040498#comment-16040498 ] 

Arek Kita commented on OAK-6312:
--------------------------------

From [~mattvryan] to discuss:
{quote}
From the perspective of an AbstractDataStoreService subclass, will the
config still be passed into the "createDataStore()" method as a Map<String,
Object> after having been read from the nstab-formatted config file?  I
assume so but wonder if that is the case.
{quote}

[~chetanm]: Is there any additional documentation we can follow or we should just be familiar with OAK-6210? Thanks!

> Unify NodeStore/DataStore configurations
> ----------------------------------------
>
>                 Key: OAK-6312
>                 URL: https://issues.apache.org/jira/browse/OAK-6312
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob, blob-plugins, composite, mk
>            Reporter: Arek Kita
>
> I've noticed recently that with many different NodeStore
> implementation (Segment, Document, Composite) but also DataStore
> implementation (File, S3, Azure) and some composite ones like
> (Hierarchical, Federated) it
> becomes more and more difficult to set up everything correctly and be
> able to know the current persistence state of repository (especially
> with pretty aged repos). The factory code/required options are more complex not only from user perspective but also from maintenance point.
> We should have the same means of *describing* layouts of Oak repository no matter if it is simple or more layered/composite instance.
> Some work has already been done in scope of OAK-6210 so I guess we have good foundations to continue working in that direction.
> /cc [~mattvryan], [~chetanm]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)