Skip to content

Commit 17fc8c7

Browse files
authored
DOCSP-37928-hidden-indexes-second-person-edit (#7090)
1 parent 5c3be3a commit 17fc8c7

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

source/core/index-hidden.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ Hidden Indexes
1616
Hidden indexes are not visible to the :doc:`query planner
1717
</core/query-plans>` and cannot be used to support a query.
1818

19-
By hiding an index from the planner, users can evaluate the potential
19+
By hiding an index from the planner, you can evaluate the potential
2020
impact of dropping an index without actually dropping the index. If the
21-
impact is negative, the user can unhide the index instead of having to
21+
impact is negative, you can unhide the index instead of having to
2222
recreate a dropped index.
2323

2424
Behavior

source/includes/fact-hidden-indexes.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
MongoDB offers the ability to hide or unhide indexes from the query planner.
2-
By hiding an index from the planner, users can evaluate the potential impact of
2+
By hiding an index from the planner, you can evaluate the potential impact of
33
dropping an index without actually dropping the index.
44

5-
If after the evaluation, the user decides to drop the index, the user
5+
If after the evaluation, the user decides to drop the index, you
66
can drop the hidden index; i.e. you do not need to unhide it first to
77
drop it.
88

source/reference/method/db.collection.hideIndex.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ Definition
2525
hidden from the query planner <index-type-hidden>` is not evaluated
2626
as part of query plan selection.
2727

28-
By hiding an index from the planner, users can evaluate the
28+
By hiding an index from the planner, you can evaluate the
2929
potential impact of dropping an index without actually dropping the
30-
index. If the impact is negative, the user can unhide the index
30+
index. If the impact is negative, you can unhide the index
3131
instead of having to recreate a dropped index. And because indexes
3232
are fully maintained while hidden, the indexes are immediately
3333
available for use once unhidden.

source/release-notes/4.4.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1972,9 +1972,9 @@ Starting in version 4.4, MongoDB adds the ability to hide or unhide
19721972
indexes from the query planner. An index hidden from the query planner
19731973
is not evaluated as part of query plan selection.
19741974

1975-
By hiding an index from the planner, users can evaluate the potential
1975+
By hiding an index from the planner, you can evaluate the potential
19761976
impact of dropping an index without having to drop the index. If the
1977-
impact is negative, the user can unhide the index instead of having to
1977+
impact is negative, you can unhide the index instead of having to
19781978
recreate a dropped index. And because indexes are fully maintained
19791979
while hidden, hidden indexes are immediately available for use once
19801980
unhidden.

0 commit comments

Comments
 (0)