Paul
My feedback
3 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
·
-
363 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
·
-
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"} ] }