Paul
My feedback
4 results found
-
15 votes
Admin mistake! Long Numbers are also still unavailable. Reopening this and I am sorry for the confusion.
An error occurred while saving the comment Paul
supported this idea
·
-
372 votes
Now in Public Preview: Introducing a Local Experience for Atlas, Atlas Search, and Atlas Vector Search with the Atlas CLI
Please feel to reply with feedback or leave comments. Happy to connect directly and include your team in our Early Access Program to provide additional help.
Paul
supported this idea
·
-
67 votes
Revisiting this request, MongoDB announced plans to support search and vector search features in both MongoDB Community Edition and MongoDB Enterprise Advanced at .local NYC 2024. Work is underway on bringing these features to our self-managed offerings.
We anticipate a public preview for search and vector search on MongoDB Community edition later in 2025 and would like to move quickly on making a GA version available towards the end of 2025 or beginning of 2026. Around the time we make search and vector search features GA for MongoDB Community Edition, we anticipate a preview release of these features for MongoDB Enterprise Advanced.
Great things are in the works! Stay tuned for updates coming soon.
Paul
supported this idea
·
-
2 votesPaul
shared this idea
·
This would be great. Right now I have a trigger to convert a field into a string conversion of that field, but it stinks to have to maintain this parity between the real number and the search meta data for it. { "field": (int) } and then { "_field": (string) }. Then in the mapping: { ... "field": {"type": "number"}, {"_field": [{"type": "string"}, {"type":"autocomplete"}]} }.
It'd be great to just be able to change the mapping to: { ... "field": [ {"type":"number"}, {"type":"string"}, {"type": "autocomplete"} ] }