Add note to geo-partitioning about excluding ranges

cockroachdb · Jan 7, 2019 · e025cf6 · e025cf6
1 parent 4771237
commit e025cf6
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/v2.1/training/geo-partitioning.md b/v2.1/training/geo-partitioning.md
@@ -395,7 +395,7 @@ To check this, run the `SHOW EXPERIMENTAL_RANGES` statement on the `vehicles` an
 {% include copy-clipboard.html %}
 ~~~ sql
 > SELECT * FROM [SHOW EXPERIMENTAL_RANGES FROM TABLE vehicles] \
-WHERE "start_key" IS NOT NULL AND "start_key" NOT LIKE '%Prefix%';
+WHERE "start_key" NOT LIKE '%Prefix%';
 ~~~
 
 ~~~
@@ -410,6 +410,10 @@ WHERE "start_key" IS NOT NULL AND "start_key" NOT LIKE '%Prefix%';
 (6 rows)
 ~~~    
 
+{{site.data.alerts.callout_info}}
+The `WHERE` clause in this query excludes the empty ranges between the city ranges. These empty ranges use the default replication zone configuration, not the zone configuration you set for the cities.
+{{site.data.alerts.end}}
+
 For added clarity, here's a key showing how nodes map to datacenters and cities:
 
 Node IDs | Datacenter | Cities

diff --git a/v2.2/training/geo-partitioning.md b/v2.2/training/geo-partitioning.md
@@ -396,7 +396,7 @@ To check this, run the `SHOW EXPERIMENTAL_RANGES` statement on the `vehicles` an
 {% include copy-clipboard.html %}
 ~~~ sql
 > SELECT * FROM [SHOW EXPERIMENTAL_RANGES FROM TABLE vehicles] \
-WHERE "start_key" IS NOT NULL AND "start_key" NOT LIKE '%Prefix%';
+WHERE "start_key" NOT LIKE '%Prefix%';
 ~~~
 
 ~~~
@@ -411,6 +411,10 @@ WHERE "start_key" IS NOT NULL AND "start_key" NOT LIKE '%Prefix%';
 (6 rows)
 ~~~    
 
+{{site.data.alerts.callout_info}}
+The `WHERE` clause in this query excludes the empty ranges between the city ranges. These empty ranges use the default replication zone configuration, not the zone configuration you set for the cities.
+{{site.data.alerts.end}}
+
 For added clarity, here's a key showing how nodes map to datacenters and cities:
 
 Node IDs | Datacenter | Cities