Atlas Search
149 results found
-
Ruby on Rails support of Atlas Search index management
Feedback from customer: "Currently we need to manage core DB indexes and atlas search indexes separately. We'd prefer to manage them all in the Rails model code but MongoID only supports core DB index configuration. We're having to use terraform for atlas search index management."
1 vote -
Data type coercion when document field type doesn't match index field type
When a document field type doesn't match the index field type, it seems to be indexed as "blank" and won't match anything. Many data types are readily convertible between type representations. It would be great if Atlas Search could do that for us and would open up richer functionality by allowing us to use operators/analyzers/etc. on types that don't normally support them.
My particular use case is to allow searching & sorting on numbers stored as strings. When creating indexes and sorting with "normal" queries, it is possible to sort numbers stored as strings by their numerical ordering rather than…
1 vote -
Token filter that removes duplicated entries
Create a token filter or a tokenizer or even an option that removes duplicate words in fields to avoid misleading scoring. For example: if I insert a document with a property "Testing testing document", another with "Testing example" and a third with "Testing foo" and I search for "Testing foo", the first document receives a higher score.1 vote -
knnBeta Limitations and Syntax
I tested the new knnBeta operator today and it worked so far.
Can we expect the current operator limitations to be gone by release?
The current limitations make it virtually impossible to use the knn operator as a replacement for previous text operators (like text).
I would prefer the filter parameter to be omitted and knn not have to be a top-level operator.1 vote -
wildcard paths in index specifications
It would make index specification easier in some cases if wildcards were possible in the paths. Yes we have dynamic indexing, but to keep the index size minimal and to be more flexible I want to index only the fields I really need. Consider the following example:
Example document:
{
foo: {
de: {
field1: 'bar',
field2: 'bar'
},
en: {
field1: 'bar',
field2: 'bar'
},
fr: {
field1: 'bar',
field2: 'bar'
},
}
}Index specification:
{
"mappings": {
"dynamic": false,
"fields": {
"foo": {
"type": "document",
"dynamic": false,
"fields": {
"$**": {
"type": "document",
"dynamic": false,
"fields": {…1 vote -
Ability to randomize score
I would like to be able to add randomness to the search results' score.
1 vote -
Ability to return all documents in a collection
I need to return all documents in a collection while boosting certain results which match my search criteria.
1 vote -
Ability to exclude documents matching a certain criteria from index
We don't do physical deletion of documents, but a logical one, flagging them by setting a value for a
deleted_atfield.We would like an option to exclude documents where that field exists and is not null from the index, because they will never be returned and are only consuming space of the index.
Currently we use a
mustNotcondition to exclude them, but of course they are still being indexed.The ideal would be to be able to define the exclusion criteria in the index definition.
1 vote -
Multiple Capture Groups in RegEx Tokenizer
Currently the RegEx tokenizer only supports to either create a token from each match or for one capture group per match. This makes it impossible to reuse parts of the text for multiple tokens, for example when you want to tokenize "13.3" into "13" as well as "13.3" (our use case is searching products where we want to find a 13.3" device by searching for 13" as well as 13.3").
1 vote -
Duplicate search index
I want to be able to easily duplicate a search index in the Atlas UI.
1 vote -
Allow retrieval of individual score from embedded document search
When using the emeddedDocuments operator to search you get a score per document, but not per embedded document. The aggregated score is either min/max/sum/mean but what I really need is the individual score from the embedded documents in order to further filter out the best matches.
1 vote -
search
Allow scoring of individual embeddedDocument searches or allow $unwind phase before $search to enable fuzzy searching for specific embeddedDocument in array of embedded documents
1 vote -
.NET Driver
It would be great if the .NET driver would support $search along with all the associated operators.
1 vote -
Support for OR Conditions
We need support for matching for one condition out of several. This is an important usecase for my requirements.
e.g. $or: [{ "airlines": "United" }, { "ticket_price": { $lte: 600.00 } }]
Thanks!
1 vote -
Provide features for array comparisons
It would be very helpful if we can lookup documents that have certain array fields that match the provided array in the query. Exact match, Any match etc should be supported. All data types should be supported.
e.g { text: { path: "city", query: ["New York", "Los Angeles", "Kansas"] } } should return all documents that have the city as ["New York", "Los Angeles", "Kansas"].
1 vote -
Filtered Indexes
Provide capability to create filtered indexes. This would allow creating tenant-specific indexes in a multi-tenant database.
While the current implementation does support this feature in a way, it requires manual maintenance of such indexes as there is an implicit assumption that each tenant would have the same fields.
Our core requirement is that each tenant can have their own set of fields. Filtered indexes would help reduce the size, hence requiring fewer system resources and possibly helping the database perform better.
1 vote -
Faster Search Index Builds
Today, my index build may take a long time (depending on the amount of documents being indexed) and I would like to see these be faster so I am able to develop and iterate faster.
Please comment current build time and preferred build time.
1 vote -
Display indexID in the UI
Just like the project ID is displayed on the Project Settings page, please display the index ID somewhere in the UI, so that we know what indexID to put when using the Atlas Search API endpoints (they require indexIDs but the UI displays only index names). That would make management and maintenance much simpler.
Unless I'm mistaken, the only way to know the indexID of an index I see in my UI is to make programmatic calls to some other API endpoints.
1 vote -
Support document-level RBAC for search query results
Users of Elastic may configure role-based security for specific indexed fields or indexed documents. For document-level security, a query filter(s) is associated with a role, and an authenticated search query provides the role. The search engine looks up RBAC rules for the given role and index combination, adds the filter or filters defined for the role and adds the filters as part of a compound search query. This allows an easy form of document-level RBAC so certain roles may search and access only a given set of documents based on one or more filter query fragments.
https://www.elastic.co/guide/en/elasticsearch/reference/current/document-level-security.html
1 vote -
Make the size bigger of Query search results
Hey, recently I saw that in find section, where all data shown, is bit smaller in view point. I mean we can't see properly entire obj. Right now we have only less screen to see it.
Here I have attached two picture of find section. Plz make the screen bigger to see more...
Hope to implement my ideas.....1 vote
- Don't see your idea?