Marcus Eagan
My feedback
20 results found
-
17 votesMarcus Eagan
shared this idea
·
-
2 votesMarcus Eagan
shared this idea
·
-
3 votes
An error occurred while saving the comment -
1 voteMarcus Eagan
shared this idea
·
-
4 votes
An error occurred while saving the comment Marcus Eagan
commented
We offer the minimumShouldMatch parameter in the should operator of the compound query. You can easily break this out by terms on the application side and set the ratio (100% or 60%) with this parameter.
See the docs here: https://docs.atlas.mongodb.com/atlas-search/compound/#mongodb-data-should
Does that work for user?
-
2 votesMarcus Eagan
shared this idea
·
-
27 votesMarcus Eagan
supported this idea
·
-
5 votesMarcus Eagan
supported this idea
·
-
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 Marcus Eagan
commented
Today, you can create a field of type number. We actually support large integers (int64) and doubles (indexDoubles boolean).
You can learn about it here: https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#number
Fuzzy and autocomplete are text operator options for the string type, so you would need to convert the type / cast it to a string in a copied field. You can do all of these operations in Atlas as well, if need be.
-
42 votes
An error occurred while saving the comment Marcus Eagan
commented
Today, you may be able to move documents in a collection that you do not want searchable to online archive.
-
1 vote
An error occurred while saving the comment Marcus Eagan
commented
While the $search stage will only be available through the aggregation pipeline for the time being, there is a user voice for adding a count stage for Atlas Search here: https://feedback.mongodb.com/forums/924868-atlas-search
Could you share more about your use case?
-
1 vote
An error occurred while saving the comment Marcus Eagan
commented
We have added Kuromoji, but it has not been added to the UI yet. Here is the list of Language Analyzers:
https://docs.atlas.mongodb.com/reference/atlas-search/analyzers/language/
-
352 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.
An error occurred while saving the comment Marcus Eagan
commented
We are working on an initiative to provide a local dev experience for our users. It is coming soon. In the meantime, there may be ways for you to use Atlas for development purposes.
Marcus Eagan
supported this idea
·
-
3 votesMarcus Eagan
supported this idea
·
-
81 votes
An error occurred while saving the comment Marcus Eagan
commented
Tyler, multi-tenancy can be accomplished easily with the filter clause within the compound operator for search and others.
I'm attaching an example query with the same message that I am posting here. Of course, the comment is not valid JSON so you would need to run the query if you want to.
This query uses the sample_restaurants.restaurants data set in Atlas and the default index. Assume that the customers here are the boroughs of New York. Below is a query by the Queens tenant for a deli specializing in Sandwiches. It returns a number of documents but only those in Queens.
Let me know if you have any questions.
/** This query uses the sample_restaurants.restaurants dataset in Atlas and the default index.
Assume that the customers here are the boroughs of New York.
Below is a query by the Queens tenant for a deli specializing in Sandwiches. It reutrns a number of documents but only those in Queens.
**/{
"index": "default",
"compound": {
"must": [
{
"text": {
"query": "Deli",
"path": "name"
}
}
],
"should": [
{
"text": {
"query": "Sandwiches",
"path": "cuisine"
}
}
],
"filter": [
{
"text": {
"query": "Queens",
"path": "borough"
}
}
]
}
} -
4 votesMarcus Eagan
supported this idea
·
-
6 votesMarcus Eagan
shared this idea
·
-
10 votesMarcus Eagan
shared this idea
·
-
5 votes
We have planned to add more analyzers.
Marcus Eagan
supported this idea
·
-
4 votesMarcus Eagan
supported this idea
·
You can get and- + or-type operators in two ways. The clunky way is to use query string. The more scalable and maintainable approach is to use compound. should is or. must is and. mustNot is and not.
Compound: https://docs.atlas.mongodb.com/atlas-search/compound/
Query String: https://docs.atlas.mongodb.com/atlas-search/queryString/
Query String is easier for people to wrap their heads around earlier, but it is far more limited and less flexible than compound.