Merge pull request #2470 from tinyspeck/update-shard-key-docs

update docs to reflect that shard keyranges can be > 1 byte

doc/Sharding.md

@@ -96,6 +96,7 @@ Start=[], End=[]: Full Key Range
 Start=[], End=[0x80]: Lower half of the Key Range.
 Start=[0x80], End=[]: Upper half of the Key Range.
 Start=[0x40], End=[0x80]: Second quarter of the Key Range.
+Start=[0xFF00], End=[0xFF80]: Second to last 1/512th of the Key Range.
 ```
 
 Two key ranges are consecutive if the end value of one range equals the
@@ -117,6 +118,14 @@ full partition:
 * 80-c0
 * c0-
 
+Shards do not need to handle the same size portion of the key space. For example, the following five shards would also be a valid full partition, albeit with a highly uneven distribution of keys.
+
+* -80
+* 80-c0
+* c0-dc00
+* dc00-dc80
+* dc80-
+
 ## Resharding
 
 In Vitess, resharding describes the process of updating the sharding

docs/sitemap.xml

@@ -21,20 +21,11 @@
   <url>
     <loc>http://vitess.io/user-guide/horizontal-sharding.html</loc>
   </url>
-  <url>
-    <loc>http://vitess.io/search/</loc>
-  </url>
-  <url>
-    <loc>http://vitess.io/about/</loc>
-  </url>
   <url>
     <loc>http://vitess.io/overview/</loc>
   </url>
   <url>
-    <loc>http://vitess.io/contributing/</loc>
-  </url>
-  <url>
-    <loc>http://vitess.io/getting-started/</loc>
+    <loc>http://vitess.io/about/</loc>
   </url>
   <url>
     <loc>http://vitess.io/terms/</loc>
@@ -42,6 +33,15 @@
   <url>
     <loc>http://vitess.io/</loc>
   </url>
+  <url>
+    <loc>http://vitess.io/search/</loc>
+  </url>
+  <url>
+    <loc>http://vitess.io/getting-started/</loc>
+  </url>
+  <url>
+    <loc>http://vitess.io/contributing/</loc>
+  </url>
   <url>
     <loc>http://vitess.io/user-guide/introduction.html</loc>
   </url>

docs/user-guide/sharding.html

@@ -388,6 +388,7 @@ value equal to or higher than 0x80 are assigned to the other shard.</p>
 <span class="nv">Start</span><span class="o">=[]</span>, <span class="nv">End</span><span class="o">=[</span>0x80<span class="o">]</span>: Lower half of the Key Range.
 <span class="nv">Start</span><span class="o">=[</span>0x80<span class="o">]</span>, <span class="nv">End</span><span class="o">=[]</span>: Upper half of the Key Range.
 <span class="nv">Start</span><span class="o">=[</span>0x40<span class="o">]</span>, <span class="nv">End</span><span class="o">=[</span>0x80<span class="o">]</span>: Second quarter of the Key Range.
+<span class="nv">Start</span><span class="o">=[</span>0xFF00<span class="o">]</span>, <span class="nv">End</span><span class="o">=[</span>0xFF80<span class="o">]</span>: Second to last 1/512th of the Key Range.
 </code></pre></div>
 <p>Two key ranges are consecutive if the end value of one range equals the
 start value of the other range.</p>
@@ -410,6 +411,16 @@ full partition:</p>
 <li>c0-</li>
 </ul>
 
+<p>Shards do not need to handle the same size portion of the key space. For example, the following five shards would also be a valid full partition, albeit with a highly uneven distribution of keys.</p>
+
+<ul>
+<li>-80</li>
+<li>80-c0</li>
+<li>c0-dc00</li>
+<li>dc00-dc80</li>
+<li>dc80-</li>
+</ul>
+
 <h2 id="resharding">Resharding</h2>
 
 <p>In Vitess, resharding describes the process of updating the sharding