Azure AI Search: How to Modify the document key to meet the validation requirements

Unif 60 Reputation points
2024-10-15T05:07:19.33+00:00

My Indexer has the error:

errorMessage details
Could not parse document. Document key cannot be longer than 1024 characters.' 'Target field 'id' is either not present_ doesn't have a value set'

The Troubleshooting common indexer errors and warnings in Azure AI Search said I should Modify the document key to meet the validation requirements.

But the question is how I can modify the document key? to make document key shorter than 1024 characters?

This is my index json config:

  "fields": [
    {
      "name": "id",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "stored": true,
      "sortable": false,
      "facetable": false,
      "key": true,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null,
      "normalizer": null,
      "dimensions": null,
      "vectorSearchProfile": null,
      "vectorEncoding": null,
      "synonymMaps": []
    },
]

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
1,069 questions
{count} votes

Accepted answer
  1. Laxman Reddy Revuri 410 Reputation points Microsoft Vendor
    2024-10-21T10:09:04.3133333+00:00

    Hi @Unif,

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer

    Ask:  Azure AI Search: How to Modify the document key to meet the validation requirements

    Solution: I changed the filename to xxx/yyy/FILE_NAME/1 to avoid a double filename (which was in Non-English).

    As a result, the error disappeared, and the indexing process of Azure AI Search was able to proceed correctly.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information. 

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue. 

     Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members. 

    0 comments No comments

0 additional answers

Sort by: Most helpful

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.