Skip to content

Conversation

@burythehammer
Copy link
Collaborator

@burythehammer burythehammer commented Mar 19, 2025

This Pull Request introduces the ability to set the Query Performance Factor field on the RedisCloud Subscription, (Pro) and related Databases.

A new schema attribute is introduced named query_performance_factor and can be set in a subscription creation plan as well as in any attached databases to that subscription.

Validation is provided to ensure that the query_performannce_factor can only be used if the modules field contains the RediSearch value. Additional validation is provided to only accept even values between 2x and 16x. This corresponds to the following:

RedisCloud /v1/query-performance-factors
https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor/

@trentrosenbaum trentrosenbaum marked this pull request as ready for review April 3, 2025 14:37
@trentrosenbaum trentrosenbaum changed the title WIP: adding in support for query performance factors on affected resources Adding in support for query performance factors on affected resources Apr 9, 2025
@burythehammer burythehammer force-pushed the feat/query_performance_factors branch from ff61fc4 to 3b5952f Compare May 15, 2025 12:26
@burythehammer burythehammer self-assigned this May 15, 2025
@burythehammer burythehammer force-pushed the feat/query_performance_factors branch from 3b5952f to 694367e Compare May 15, 2025 14:50
@burythehammer burythehammer changed the base branch from main to develop May 15, 2025 14:51
@burythehammer burythehammer merged commit d38579a into develop May 16, 2025
8 checks passed
@burythehammer burythehammer deleted the feat/query_performance_factors branch August 20, 2025 09:26
burythehammer added a commit that referenced this pull request Nov 10, 2025
Adding in support for query performance factors on affected resources
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

Successfully merging this pull request may close these issues.

3 participants