Skip to content

Commit 15bc41d

Browse files
asya999jeff-allen-mongo
authored andcommitted
DOCSP-14387 Removing incorrect example
1 parent 193c87a commit 15bc41d

File tree

1 file changed

+0
-32
lines changed

1 file changed

+0
-32
lines changed

source/reference/method/sh.updateZoneKeyRange.txt

Lines changed: 0 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -219,38 +219,6 @@ with the ``alpha`` zone:
219219
"alpha"
220220
)
221221

222-
If you wanted to create a range on values of ``b`` only, you must specify
223-
the entire range of ``a`` when creating ranges. For example, the following
224-
operations create two ranges on ``b`` and associates them to the
225-
``beta`` zone.
226-
227-
.. note::
228-
229-
The previously defined range conflicts with the ranges defined in this
230-
example. Issue the :method:`sh.removeRangeFromZone()` operation to remove an
231-
existing conflicting range.
232-
233-
.. code-block:: javascript
234-
235-
sh.updateZoneKeyRange(
236-
"exampledb.collection",
237-
{ a : MinKey, b : 1 },
238-
{ a : MaxKey, b: 10 },
239-
"alpha"
240-
);
241-
242-
sh.updateZoneKeyRange(
243-
"exampledb.collection",
244-
{ a : MinKey, b : 10 },
245-
{ a : MaxKey, b: 20 },
246-
"beta"
247-
);
248-
249-
:bsontype:`MinKey` always compares as lower than every other possible value,
250-
while :bsontype:`MaxKey` always compares as higher than every other possible
251-
value. Using these special values for the lower and upper bounds of the range
252-
captures the entire possible value space of ``a``.
253-
254222
.. _pre-define-zone-range-example:
255223

256224
Pre-Define Zones and Zone Ranges for an Empty or Non-Existing Collection

0 commit comments

Comments
 (0)