Skip to content

Conversation

gregstuder
Copy link

Unless I'm missing something here, the issue we identified with v:0 indexes isn't related to upgrade at all, and is no more or less likely after the upgrade. We definitely want to encourage index upgrade, but not doing so won't make things worse.

Mention this because seeing customer concern about this warning in the docs.

Unless I'm missing something here, the issue we identified with v:0 indexes isn't related to upgrade at all, and is no more or less likely after the upgrade.  We definitely want to encourage index upgrade, but not doing so won't make things worse.

Mention this because seeing customer concern about this warning in the docs.
@tychoish
Copy link
Contributor

merged!

@tychoish tychoish closed this Jul 16, 2013
mongo-cr-bot pushed a commit that referenced this pull request May 18, 2022
* DOCSP-22441-pre-post-image-downgrade

* DOCSP-22441-pre-post-image-downgrade

* DOCSP-22441-pre-post-image-downgrade

Co-authored-by: jason-price-mongodb <[email protected]>
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jul 22, 2025
… v6.15 Node CC (#1114)

* DOCSP-44947 TOC Relabel (#923)

* DOCSP-44947 TOC Relabel

* font:

* edit

* Mike's suggestion

(cherry picked from commit 09afc55)

* backport

* [Backport v6.14] DOCSP-49652 Backport v6.15 Node CC (#1102) (#1110) (#1112)

* DOCSP-49652 Backport v6.15 Node CC (#1102)

* Backport v6.15 Node CC

* first full pass

* add usage examples to TOC

* save TOC

* edits

* extra ref edits

* redirect fix

* monitoring edits

* auth and montioring

* edits

* redirects

* edit redirects for all back ports

(cherry picked from commit 1067a9b)

* generate deploy

(cherry picked from commit fc2f38b)
(cherry picked from commit 80dd1ff)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants