[DOCS-13982] Investigate changes in SERVER-47081: Remove support for the geoSearch command and geoHaystack indexes Created: 12/Nov/20 Updated: 13/Nov/23 Due: 07/May/21 Resolved: 17/May/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Andrew Feierabend (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 2 years, 38 weeks, 2 days ago | ||||||||||||||||
| Epic Link: | DOCSP-9747 | ||||||||||||||||
| Story Points: | 2 | ||||||||||||||||
| Description |
DescriptionDownstream Change Summary Support for the geoSearch command and haystack indexes has been removed in version 4.9. Any pre-existing haystack indexes will be deleted as part of the upgrade to FCV 4.9 and above. Description of Linked Ticket These features are planned for deprecation under Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 17/May/21 ] |
|
Author: {'name': 'andf-mongodb', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}Message: |
| Comment by Jeffrey Allen [ 29/Apr/21 ] |
|
david.storch , yeah, when we update our Compatibility Notes page with info about the deletion of haystack indexes and geoSearch, we could update the dochub link to point to that new content if that would be preferable. Whether we do or do not, the URL would remain the same, so still no action required in |
| Comment by David Storch [ 29/Apr/21 ] |
|
Thanks jeffrey.allen. Regarding the dochub link – do you think it should permanently point to the page for 2d indexes? Or would we make it direct users to a page that describes the deprecation/deletion of haystack indexes and geoSearch? Even if we did make such a change, is there any reason to make any changes to the message logged by the server? It seems to me that there is not, and we can close |
| Comment by Jeffrey Allen [ 29/Apr/21 ] |
|
Ah, and with |
| Comment by Jeffrey Allen [ 28/Apr/21 ] |
|
Hi david.storch and mihai.andrei ! 100% agree that this is a key user-facing update coming in 5.0. We will discuss this ticket in our next planning meeting (Monday) and will have a better sense of when we will address this ticket then. Rest assured it will get documented for the v5.0 release! |
| Comment by David Storch [ 28/Apr/21 ] |
|
Hi jeffrey.allen! Could we get an update on the status of this ticket? Since 5.0 is approaching, it seems like documenting the removal of this functionality is important. We would also like to understand whether there is anything that needs to be done on our end under CC mihai.andrei |
| Comment by David Storch [ 12/Nov/20 ] |
|
We should make sure that the upgrade instructions mention that you should ensure your application is not using geoSearch or geoHaystack prior to upgrade to a version 4.9 or above. And I guess the release notes should also mention that we have removed support for this feature. |
| Comment by Mihai Andrei [ 12/Nov/20 ] |
|
As part of this work, we need a new dochub link that points to the page which documents the removal of support for geoSearch/geoHaystack. |