What an external table keyed on base-revision keys should do with each row whose element split:
copy-to-all
largest-share
shares
orphan-on-split
A merge always maps every base row onto the one head key, whatever the policy: the data of k elements now describes one.
merge
What an external table keyed on base-revision keys should do with each row whose element split:
copy-to-all— every piece inherits the row.largest-share— only the piece with the largest volume share inherits it; withoutsharesthe row is orphaned rather than guessed.orphan-on-split— the row is orphaned; only 1:1 relations rekey.A
mergealways maps every base row onto the one head key, whatever the policy: the data of k elements now describes one.