Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6312

Unify NodeStore/DataStore configurations

    XMLWordPrintableJSON

    Details

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                arkadius Arek Kita
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: