Issue with FullTextPolicy Persistence on CosmosDB Container

David West 5 Reputation points
2024-12-17T19:39:08.77+00:00

I am experiencing an issue when adding a FullTextPolicy to an existing CosmosDB container. The full text support feature has been enabled on the account. Although the full text index is created successfully, the full text policy does not persist, and consequently, the full text functions do not work as expected. Has anyone encountered a similar issue or can provide guidance on how to resolve this? Any help would be greatly appreciated.

Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
1,710 questions
{count} votes

2 answers

Sort by: Most helpful
  1. hossein jalilian 9,310 Reputation points
    2024-12-17T20:16:52.4866667+00:00

    Thanks for posting your question in the Microsoft Q&A forum.

    To troubleshoot and potentially resolve the issue:

    • Double-check that the full text support feature is enabled at the account level.
    • Verify your indexing policy configuration, ensuring it includes the necessary paths for full text indexing.
    • Monitor your container for any policy reversions or changes.
    • Consider recreating the container with the desired FullTextPolicy if the issue persists.

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful


  2. Mahesh Kurva 1,470 Reputation points Microsoft Vendor
    2024-12-18T02:18:03.9566667+00:00

    Hi @David West,

    Welcome to Microsoft Q&A forum.

    Apologies for causing the issue.

    I have tried all of the above, even creating a new container. No luck. Anything else I can try?

    Here are a few additional suggestions that might help:

    • Since full text search is still in preview, there might be regional limitations or specific configurations required. Ensure that your region supports this feature and that all necessary configurations are in place.

    For more information, please refer the document: https://learn.microsoft.com/en-us/azure/cosmos-db/gen-ai/full-text-search?source=recommendations

    • If your queries involve multiple partitions, ensure that full text search supports cross-partition queries in your setup. There have been reports of issues when trying to use full text functions across partitions.
    • Instead of using the Azure portal, try creating the container and applying the FullTextPolicy using the Azure CLI or an SDK (like .NET, Python, etc.). Sometimes, the portal might not reflect certain configurations correctly.

    For more information, please refer the document: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-create-container

    Hope this helps. Do let us know if you any further queries.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.