Skip to content

Commit 9f80644

Browse files
asya999jeff-allen-mongo
authored andcommitted
DOCSP-14387 Removing incorrect example
1 parent 875bf61 commit 9f80644

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
@@ -257,38 +257,6 @@ with the ``alpha`` zone:
257257
"alpha"
258258
)
259259

260-
If you wanted to create a range on values of ``b`` only, you must specify
261-
the entire range of ``a`` when creating ranges. For example, the following
262-
operations create two ranges on ``b`` and associates them to the
263-
``beta`` zone.
264-
265-
.. note::
266-
267-
The previously defined range conflicts with the ranges defined in this
268-
example. Issue the :method:`sh.removeRangeFromZone()` operation to remove an
269-
existing conflicting range.
270-
271-
.. code-block:: javascript
272-
273-
sh.updateZoneKeyRange(
274-
"exampledb.collection",
275-
{ a : MinKey, b : 1 },
276-
{ a : MaxKey, b: 10 },
277-
"alpha"
278-
);
279-
280-
sh.updateZoneKeyRange(
281-
"exampledb.collection",
282-
{ a : MinKey, b : 10 },
283-
{ a : MaxKey, b: 20 },
284-
"beta"
285-
);
286-
287-
:bsontype:`MinKey` always compares as lower than every other possible value,
288-
while :bsontype:`MaxKey` always compares as higher than every other possible
289-
value. Using these special values for the lower and upper bounds of the range
290-
captures the entire possible value space of ``a``.
291-
292260
.. _pre-define-zone-range-example:
293261
.. _pre-define-zone-range-hashed-example:
294262

0 commit comments

Comments
 (0)