You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2011/09/06 18:40:20 UTC
svn commit: r1165757 - /subversion/branches/fs-successor-ids/BRANCH-README
Author: danielsh
Date: Tue Sep 6 16:40:20 2011
New Revision: 1165757
URL: http://svn.apache.org/viewvc?rev=1165757&view=rev
Log:
On the fs-successor-ids branch, update BRANCH-README.
* BRANCH-README (fsfs whiteboard): Document the different semantics of shards.
Modified:
subversion/branches/fs-successor-ids/BRANCH-README
Modified: subversion/branches/fs-successor-ids/BRANCH-README
URL: http://svn.apache.org/viewvc/subversion/branches/fs-successor-ids/BRANCH-README?rev=1165757&r1=1165756&r2=1165757&view=diff
==============================================================================
--- subversion/branches/fs-successor-ids/BRANCH-README (original)
+++ subversion/branches/fs-successor-ids/BRANCH-README Tue Sep 6 16:40:20 2011
@@ -118,6 +118,14 @@ node_rev_id --+ | rQ | |
Each type of file is described below in detail.
+-- Common aspects --
+
+Sharding. All three kinds of files are sharded in a manner similar to
+revision files. However, since revision 0 never creates successors of
+anything, it is not in any shard. The Nth shard contains data for
+noderevs in revisions { r | (r-1) % shard_size == N }: so, 1..1000,
+1001..2000, etc.
+
-- Node-revision-ID map files --
The purpose of node-revision-id map files is to facilitate lookup