You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as a username has some special character, no documents are found in the fulltext search. This effectively breaks fulltext search for all AD/LDAP users, which makes nextcloud unsuitable for use in corporate environments.
This is caused by the filter restricting documents by user permissions in
The term query on users or owner does not find usernames that do not only consist of characters and digits because the type of the users and owner fields are text:
As soon as a username has some special character, no documents are found in the fulltext search. This effectively breaks fulltext search for all AD/LDAP users, which makes nextcloud unsuitable for use in corporate environments.
This is caused by the filter restricting documents by user permissions in
fulltextsearch_elasticsearch/lib/Service/SearchMappingService.php
Line 307 in 91f9440
The term query on users or owner does not find usernames that do not only consist of characters and digits because the type of the users and owner fields are text:
When using the term query on text fields, the searched term is analyzed (see the big fat warning here: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-term-query.html) and does not match. Either fix the filter to use the subfield users.keyword and owner.keyword:
or change the field type to keyword.
The text was updated successfully, but these errors were encountered: