Description
It would be good if the NodeBuilder mechanism could be more tightly integrated with the SegmentMK internals through the SegmentNodeBuilder class. The primary benefit of this would be to implement the auto-flushing functionality enabled by OAK-659.
Additionally, it should for example be possible to automatically write-ahead parts of transient change set to segments or to make the getNodeState() call always return SegmentNodeState s instead of having to repeatedly use the MutableNodeState.snapshot() mechanism that's currently dragging performance in some of our benchmarks (most notably XML imports).