mirror of
https://github.com/scylladb/scylladb.git
synced 2026-05-30 11:36:54 +00:00
" Choosing the max-result-size for unlimited queries is broken for unknown scheduling groups. In this case the system limit (unlimited) will be chosen. A prime example of this break-down is when service levels are used. This series fixes this in the same spirit as the similar semaphore selection issue (#8508) was fixed: use the user limit as the fall-back in case of unknown scheduling groups. To ensure future fixes automatically apply to both query-classification related configurations, selecting the max result size for unlimited queries is now delegated to the database, sharing the query classification logic with the semaphore selection. Fixes: #8591 Tests: unit(dev) " * 'query-max-size-service-level-fix/v2' of https://github.com/denesb/scylla: service/storage_proxy: get_max_result_size() defer to db for unlimited queries database: add get_unlimited_query_max_result_size() query_class_config: add operator== for max_result_size database: get_reader_concurrency_semaphore(): extract query classification logic