Details
-
Technical task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
The FileStore constructor consists of more than 150 LoC and is a mess as it depends on the order of initialisation, calls overrideable methods handles different concerns (read only vs. read / write) etc.
We should up with a cleaner way of instantiating a file store.
Attachments
Attachments
Issue Links
- is related to
-
OAK-4102 Break cyclic dependency of FileStore and SegmentTracker
- Closed