[
https://issues.apache.org/jira/browse/OAK-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254570#comment-15254570
]
Michael Dürig commented on OAK-4243:
------------------------------------
In the fix for OAK-3348 I left a couple of {{FIXME OAK-3348}} tags. I now
reported separate issues for most of them so we can discuss matters without
mixing concerns. I also updated the issue reference in the FIXME tags
accordingly:
* Break cyclic dependency of FileStore and SegmentTracker (OAK-4102)
* Less verbose logging during revision gc (OAK-4165)
* Refactor / rework compaction strategies (OAK-4276)
* Finalise de-duplication caches (OAK-4277)
* Fix backup and restore (OAK-4278)
* Rework offline compaction (OAK-4279)
* Compaction cannot be cancelled (OAK-4280)
* Rework memory estimation for compaction (OAK-4281)
* Make the number of retained gc generation configurable (OAK-4282)
* Align GCMonitor API with implementation (OAK-4283)
* Garbage left behind when compaction does not succeed (OAK-4284)
* Align cleanup of segment id tables with the new cleanup strategy (OAK-4285)
* Rework failing tests in CompactionAndCleanupIT (OAK-4286)
* Disable / remove SegmentBufferWriter#checkGCGen (OAK-4287)
* TarReader.calculateForwardReferences only used by oak-run graph tool
(OAK-4288)
* Remove the gc generation from the segment meta data (OAK-4289)
* Update segment parser to work with the new segment format (OAK-4290)
* FileStore.flush prone to races leading to corruption (OAK-4291)
* Document Oak segment next (OAK-4292)
* Refactor / rework compaction gain estimation (OAK-4293)
* Consider making FileStore.writer volatile (OAK-4294)
* Proper versioning of storage format (OAK-4295)
> Oak Segment Next Module
> -----------------------
>
> Key: OAK-4243
> URL: https://issues.apache.org/jira/browse/OAK-4243
> Project: Jackrabbit Oak
> Issue Type: Epic
> Components: segment-next
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 1.6
>
>
> There is a couple of issues requiring us to change the segment format in a
> non compatible way (OAK-3348, OAK-2896, OAK-2498, OAK-4201).
> We should introduce a new module here
> * to minimise ripple effect on concurrent development work in other parts of
> Oak and upstream projects
> * to be able to cleanly migrate existing repositories via a side grading
> * to cleanly separate breaking changes from the existing code base
> The plan is roughly to:
> * Create new module (called {{oak-segment-next}} for now, will discuss names
> later)
> * Apply patch prepared for OAK-3348
> * Discuss and decide on final name and refactor accordingly
> * Reactor affected tooling such that the targeted segment store can be
> specified via an option. Keep default at {{oak-segment}}.
> * Once sufficiently stabilised, deprecate {{oak-segment}}. Make this one the
> default in switch the default target for tooling.
> * Define and implement migration path
> I will create respective issues as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
