Azure Redis Enterprise RediSearch results limited to 200 - How to adjust MAXEXPANSIONS?

Question

Azure Redis Enterprise RediSearch results limited to 200 - How to adjust MAXEXPANSIONS?

Daram, Manikanta 0

We have an index in Azure Redis Enterprise Cache and are using the RediSearch module. When searching by a field name, the query is only returning 200 records.

We suspect there may be a configuration parameter called MAXEXPANSIONS that could be affecting this, but we are unable to view any configuration details from the RedisInsight console. Additionally, there is no option to log in directly to the Redis cluster to retrieve this information from azure portal.

I tried checking azure documentation and could not find any other details about this.

Example Query :

FT.SEARCH index_name "@filendname:keywordname*"

Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-21T08:04:24.87+00:00
Hi Daram, Manikanta,

It seems the issue you are facing with the RediSearch module in Azure Redis Enterprise Cache might be related to the MAXEXPANSIONS parameter. Below are the steps to help you resolve this

1.Check MAXEXPANSIONS Parameter:

Ensure that the MAXEXPANSIONS parameter is set to a value that allows for the desired number of records to be returned. You can adjust this parameter in your RediSearch configuration.

Example configuration change:

FT.CONFIG SET MAXEXPANSIONS 1000

2.Verify Configuration in RedisInsight:

If you are unable to view configuration details from the RedisInsight console, you might need to check the configuration directly in your Redis instance using the Redis CLI or API

3.Example Query:

Ensure that your query syntax is correct and that the MAXEXPANSIONS parameter is set appropriately.

FT.SEARCH index_name "@filendname:keywordname*" MAXEXPANSIONS 1000

I hope this information helps. Please do let us know if you have any further queries.
Daram, Manikanta 0 Reputation points

2025-04-21T08:36:49.9533333+00:00

Thank You @Prasad Chaganti . Here is the problem, we already tried to set the same, and it says unknown command FT.CONFIG .Other commands like FT.SEARCH, FT.AGGREGATE and FT.INFO commands work fine.

I also tried to set the MAXEXPANSIONS along with the search query(FT.SEARCH index_name "@filendname:keywordname*" MAXEXPANSIONS 1000), and here is the issue.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-22T01:09:44.19+00:00
Hi Daram, Manikanta,

Sorry for the inconvenience.

It appears that the FT.CONFIG command has been deprecated in RediSearch version 8.0.0 and can be replaced by the CONFIG GET command when migrating or writing new code. This might be the reason why you are encountering the "unknown command" error.

1.Use CONFIG GET Instead of FT.CONFIG:

Example Command:

CONFIG GET MAXEXPANSIONS

2.Set MAXEXPANSIONS in the Query:

You can set the MAXEXPANSIONS parameter directly in your search query.

Example query:

FT.SEARCH index_name "@filendname:keywordname*" MAXEXPANSIONS 1000

Here is an example of how you can use Python to connect to Redis and set the MAXEXPANSIONS parameter:

import redis # Connect to Redis redis_client = redis.StrictRedis( host='your_redis_host', port=6379, password='your_redis_password', ssl=True ) # Set MAXEXPANSIONS parameter redis_client.execute_command('CONFIG SET MAXEXPANSIONS 1000') # Perform search query result = redis_client.execute_command('FT.SEARCH', 'index_name', '@filendname:keywordname*', 'MAXEXPANSIONS', 1000) print(result)

I hope this information helps. Please do let us know if you have any further queries.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-23T00:42:18.34+00:00

Hi Daram, Manikanta,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Daram, Manikanta 0 Reputation points

2025-04-23T09:49:08.1566667+00:00

Thank You for the deatils @Prasad Chaganti . But no luck here.

CONFIG GET MAXEXPANSIONS

CONFIG SET MAXEXPANSIONS 1000

MAXEXPANSION with ft.search

After the data reload and index recreation, it seems to work fine for more than 200 records. But, when we perform a contains search or search using part of the field, it's not returning all the expected results.
Mahesh Kurva 4,070 Reputation points Microsoft External Staff Moderator

2025-04-24T05:46:27.9833333+00:00

Hi Daram, Manikanta,

I kindly request you to provide the details mentioned in the private message so we can identify the root cause and address the issue effectively.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-25T09:06:56.5633333+00:00

Hi Daram, Manikanta,
Could you please share the requested details mentioned in the Private message.
Thanks.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-28T02:44:46.12+00:00

Hi Daram, Manikanta,

We haven’t heard from you on the last response, I kindly request you to provide the details mentioned in the private message, Thanks.
Daram, Manikanta 0 Reputation points

2025-05-01T09:34:10.19+00:00

@Prasad Chaganti Shared the required details. Please let me know if any other details required here or if possible solution.
SSingh-MSFT 16,281 Reputation points Moderator

2025-05-12T11:25:51.84+00:00

Hi Daram, Manikanta •,

As per the official documentation https://redis.io/docs/latest/develop/interact/search-and-query/advanced-concepts/query_syntax/

Expansion is limited to 200 terms or less. You can change this number by using the **MAXEXPANSIONS** setting on the module command line.

Note

The FT.CONFIG command is not supported for updating module configuration parameters. However, this can be achieved by passing in arguments configuring the modules when using management APIs. For instance, you can see samples of configuring the ERROR_RATE and INITIAL_SIZE properties of the RedisBloom module using the args parameter with the REST API, Azure CLI, or PowerShell.

I am checking internally on the ask.

Will update here, thanks for your patience.

2 answers

Your answer

Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-21T08:04:24.87+00:00

Hi Daram, Manikanta,

It seems the issue you are facing with the RediSearch module in Azure Redis Enterprise Cache might be related to the MAXEXPANSIONS parameter. Below are the steps to help you resolve this

1.Check MAXEXPANSIONS Parameter:

Ensure that the MAXEXPANSIONS parameter is set to a value that allows for the desired number of records to be returned. You can adjust this parameter in your RediSearch configuration.

Example configuration change:

FT.CONFIG SET MAXEXPANSIONS 1000

2.Verify Configuration in RedisInsight:

If you are unable to view configuration details from the RedisInsight console, you might need to check the configuration directly in your Redis instance using the Redis CLI or API

3.Example Query:

Ensure that your query syntax is correct and that the MAXEXPANSIONS parameter is set appropriately.

FT.SEARCH index_name "@filendname:keywordname*" MAXEXPANSIONS 1000

I hope this information helps. Please do let us know if you have any further queries.
Daram, Manikanta 0 Reputation points

2025-04-21T08:36:49.9533333+00:00

Thank You @Prasad Chaganti . Here is the problem, we already tried to set the same, and it says unknown command FT.CONFIG .Other commands like FT.SEARCH, FT.AGGREGATE and FT.INFO commands work fine.

I also tried to set the MAXEXPANSIONS along with the search query(FT.SEARCH index_name "@filendname:keywordname*" MAXEXPANSIONS 1000), and here is the issue.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-22T01:09:44.19+00:00

Hi Daram, Manikanta,

Sorry for the inconvenience.

It appears that the FT.CONFIG command has been deprecated in RediSearch version 8.0.0 and can be replaced by the CONFIG GET command when migrating or writing new code. This might be the reason why you are encountering the "unknown command" error.

1.Use CONFIG GET Instead of FT.CONFIG:

Example Command:

CONFIG GET MAXEXPANSIONS

2.Set MAXEXPANSIONS in the Query:

You can set the MAXEXPANSIONS parameter directly in your search query.

Example query:

FT.SEARCH index_name "@filendname:keywordname*" MAXEXPANSIONS 1000

Here is an example of how you can use Python to connect to Redis and set the MAXEXPANSIONS parameter:

import redis # Connect to Redis redis_client = redis.StrictRedis( host='your_redis_host', port=6379, password='your_redis_password', ssl=True ) # Set MAXEXPANSIONS parameter redis_client.execute_command('CONFIG SET MAXEXPANSIONS 1000') # Perform search query result = redis_client.execute_command('FT.SEARCH', 'index_name', '@filendname:keywordname*', 'MAXEXPANSIONS', 1000) print(result)

I hope this information helps. Please do let us know if you have any further queries.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-23T00:42:18.34+00:00

Hi Daram, Manikanta,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Daram, Manikanta 0 Reputation points

2025-04-23T09:49:08.1566667+00:00

Thank You for the deatils @Prasad Chaganti . But no luck here.

CONFIG GET MAXEXPANSIONS

CONFIG SET MAXEXPANSIONS 1000

MAXEXPANSION with ft.search

After the data reload and index recreation, it seems to work fine for more than 200 records. But, when we perform a contains search or search using part of the field, it's not returning all the expected results.
Mahesh Kurva 4,070 Reputation points Microsoft External Staff Moderator

2025-04-24T05:46:27.9833333+00:00

Hi Daram, Manikanta,

I kindly request you to provide the details mentioned in the private message so we can identify the root cause and address the issue effectively.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-25T09:06:56.5633333+00:00

Hi Daram, Manikanta,
Could you please share the requested details mentioned in the Private message.
Thanks.
Prasad Chaganti 760 Reputation points Microsoft External Staff Moderator

2025-04-28T02:44:46.12+00:00

Hi Daram, Manikanta,

We haven’t heard from you on the last response, I kindly request you to provide the details mentioned in the private message, Thanks.
Daram, Manikanta 0 Reputation points

2025-05-01T09:34:10.19+00:00

@Prasad Chaganti Shared the required details. Please let me know if any other details required here or if possible solution.
SSingh-MSFT 16,281 Reputation points Moderator

2025-05-12T11:25:51.84+00:00

Hi Daram, Manikanta •,

As per the official documentation https://redis.io/docs/latest/develop/interact/search-and-query/advanced-concepts/query_syntax/

Expansion is limited to 200 terms or less. You can change this number by using the **MAXEXPANSIONS** setting on the module command line.

Note

The FT.CONFIG command is not supported for updating module configuration parameters. However, this can be achieved by passing in arguments configuring the modules when using management APIs. For instance, you can see samples of configuring the ERROR_RATE and INITIAL_SIZE properties of the RedisBloom module using the args parameter with the REST API, Azure CLI, or PowerShell.

I am checking internally on the ask.

Will update here, thanks for your patience.

Answer 1

Hi @Daram, Manikanta ,

I have checked with the internal team and it is confirmed by them that the CONFIG command is blocked on Azure Cache for Redis Enterprise as mentioned here: How to configure Azure Cache for Redis - Azure Cache for Redis | Microsoft Learn.

We are sorry about the inconvenience.

You may raise a feedback request with the concerned team here so that they can prioritize this feature: https://feedback.azure.com/d365community/forum/a96a82f3-0c25-ec11-b6e6-000d3a4f07b8

Do let us know if you have more queries.

Thanks

Answer 2

Daram, Manikanta 0

The latest update on the issue is that we cannot set/run the FT.CONFIG commands and its blocked from the azure end.

Here is the reference :

https://learn.microsoft.com/en-us/azure/redis/redis-modules

User's image

Regarding the search issue(part of the string in Redis not providing the exact result and a mismatch between the actual results and the results returned by Redis), we are working with the Azure team to fix the issue.

Share via

Azure Redis Enterprise RediSearch results limited to 200 - How to adjust MAXEXPANSIONS?

2 answers

Your answer