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
TokenClassificationRecord metadata menu seems to limit number of entries to 100 even if there are more in the dataset. #1387
Comments
Hi @coreyelowsky and thanks a lot for all of your feedback. The number of allowed metadata fields is configurable by the I would like to know if you are able to manage a larger number of these data. We can also consider expanding the maximum number of metadata fields allowed, although it could affect the performance of the search engine. |
What I meant was not for more than 50 different metadata fields. But for just one specific metadata field, we have more than 100 unique values. As in the image above, for the specific metadata field called 'note_id', only 100 unique values show up in that dropdown shown, when we really have many more unique values for that specific field. Unless we mean the same thing? |
Ok, got it. Yes, we've set a limit to a max number of results for metadata filters, since they can directly impact performance. We will increase the default value. And we can allow configuration by env var in future releases. |
fix #1387 This PR improves the performance of filter selectors by adding lazy loading and rendering only when they are visible.
See #1387 This PR improves the performance of filter selectors by adding lazy loading and rendering only when they are visible.
It seems as though the metadata drop down menu limits the amount of entries to only 100. Is it possible to expand this amount?
The text was updated successfully, but these errors were encountered: