Author: hartmannathan
Date: Fri Apr 3 03:02:18 2020
New Revision: 1876070
URL: http://svn.apache.org/viewvc?rev=1876070&view=rev
Log:
1.14 release notes: Document addition of 'svnadmin build-repcache' command.
* docs/release-notes/1.14.html
(#new-feature-compatibility-table): Expand the stub added by danielsh in
r1875975 for this new subcommand.
(#svnadmin-build-repcache): New section.
Modified:
subversion/site/publish/docs/release-notes/1.14.html
Modified: subversion/site/publish/docs/release-notes/1.14.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.14.html?rev=1876070&r1=1876069&r2=1876070&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.14.html (original)
+++ subversion/site/publish/docs/release-notes/1.14.html Fri Apr 3 03:02:18
2020
@@ -128,11 +128,11 @@ and what impact these changes may have.<
<td>any FSFS repo</td>
<td></td></tr>
<tr>
- <td><tt>svnadmin build-repcache</tt></td>
- <td>TODO</td>
- <td>TODO</td>
- <td>TODO</td>
- <td class="todo">TODO: write a section for this</td></tr>
+ <td><a href="#svnadmin-build-repcache"><tt>svnadmin
build-repcache</tt></a></td>
+ <td>n/a</td>
+ <td>1.14</td>
+ <td>FSFS version 6</td>
+ <td></td></tr>
<tr>
<td>
<a href="#shelving">Shelving (experimental)</a>
@@ -258,6 +258,56 @@ but excluding FSFS indexes. For example:
<p>(See <a href="http://svn.apache.org/r1857624";>r1857624</a>.)</p>
</div> <!-- svnadmin-rev-size -->
+<div class="h3" id="svnadmin-build-repcache">
+<h3>New <tt>svnadmin build-repcache</tt> command
+ <a class="sectionlink" href="#svnadmin-build-repcache"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>Representation Sharing (also called rep-sharing) is a data storage
+de-duplication feature first introduced in Subversion 1.6. It reduces the disk
+size of a repository by storing duplicate data only once. (See <a
+href="https://issues.apache.org/jira/browse/SVN-2286";>issue #2286</a>.)</p>
+
+<p>This optional feature is enabled by default. It relies on a rep-cache
+database, which Subversion automatically maintains with the repository, to
+identify duplicate pieces of data.</p>
+
+<p>Over time, some administrators have disabled and/or re-enabled rep-sharing,
+which has the effect of excluding from the rep-cache any revisions that were
+committed while the feature was disabled.</p>
+
+<p>Subversion 1.14 introduces a new <tt>svnadmin build-repcache</tt>
+subcommand, which administrators can use to populate any missing entries in
+the rep-cache database for a specified revision range (or all revisions). (See
+<a href="http://svn.apache.org/r1875921";>r1875921</a>.)</p>
+
+<p>For example, to process revisions 20 through 25, inclusive, and ensure that
+their data is known to the rep-cache:</p>
+
+<pre>
+ $ svnadmin build-repcache /path/to/repo -r20:25
+ * Processed revision 20.
+ * Processed revision 21.
+ * Processed revision 22.
+ * Processed revision 23.
+ * Processed revision 24.
+ * Processed revision 25.
+</pre>
+
+<p>If only one revision argument is given, <tt>svnadmin build-repcache</tt>
+will process that revision only:</p>
+
+<pre>
+ $ svnadmin build-repcache /path/to/repo -r20
+ * Processed revision 20.
+</pre>
+
+<p>If no revision argument is given, <tt>svnadmin build-repcache</tt> will
+process all revisions.</p>
+
+</div> <!-- svnadmin-build-repcache -->
+
</div> <!-- new-features -->
<div class="h2" id="enhancements">
