Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Project Search Configuration #4377

Open
kazoompa opened this issue Dec 2, 2022 · 0 comments
Open

Add Project Search Configuration #4377

kazoompa opened this issue Dec 2, 2022 · 0 comments

Comments

@kazoompa
Copy link
Member

kazoompa commented Dec 2, 2022

Although project documents are not part of the search pages but if a Mica user cusrtomizes the Project schema, there is no way of deciding wether a field is a keyword or not. Fields that are used in sorting query results must be of type keyword (old analyzed).

Current use-case is for CanCOLD where their Project schema has several new fields and the listing is sorted on a custom field which by default is a string. To remedy this, administrator needs to manually change the mapping and reindex all projects. This solution however is temporary since a Index All will destroy the index and the default mapping will once more break the sorting.

A usedful feature to preceed/follow: #3219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant