jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Updated] (OAK-6312) Unify NodeStore/DataStore configurations
Date Tue, 24 Apr 2018 09:12:00 GMT

     [ https://issues.apache.org/jira/browse/OAK-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dürig updated OAK-6312:
-------------------------------
    Labels: configuration production technical_debt  (was: configuration production)

> 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, documentmk, rdbmk, segment-tar
>            Reporter: Arek Kita
>            Priority: Major
>              Labels: configuration, production, technical_debt
>
> 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
(v7.6.3#76005)

Mime
View raw message