[OAK-6312] Unify NodeStore/DataStore configurations

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: blob, blob-plugins, composite, documentmk, rdbmk, segment-tar
• Labels: configuration production technical_debt
• Assignee: Unassigned
• Reporter: Arek Kita
• Created: 07/Jun/17 08:21
• Updated: 24/Apr/18 09:11

Description

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 Matt Ryan, Chetan Mehrotra

Issue Links

• relates to: OAK-6210 Provide a consistent and extensible way to handle oak-run options while creating NodeStore
• links to: Our discussion on oak-dev related to that topic