I never really understood Prolly Trees. With content-defined chunking (which is the only addition to regular b-trees), you always need a maximum size because it is possible for pathological content to not ever have a boundary (therefore you get one massive chunk, or for trees one massive branch node).
However once you have chunks of fixed size (the maximum) instead of content-defined sizes, changes to the content become non-local: a change in one part of the data might change an arbitrary number of following chunks/nodes.
Did they find a solution to that? Did they ignore it?
However once you have chunks of fixed size (the maximum) instead of content-defined sizes, changes to the content become non-local: a change in one part of the data might change an arbitrary number of following chunks/nodes.
Did they find a solution to that? Did they ignore it?