Update search-howto-index-one-to-many-blobs.md

Updated with limitations of deletion operations.

Author: gmndrg

articles/search/search-howto-index-one-to-many-blobs.md

@@ -11,7 +11,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 01/18/2025
+ms.date: 05/19/2025
 ---
 
 # Indexing blobs and files to produce multiple search documents
@@ -24,6 +24,7 @@ When you use any of these parsing modes, the new search documents that emerge mu
 
 To address this problem, the blob indexer generates an `AzureSearch_DocumentKey` that uniquely identifies each child search document created from the single blob parent. This article explains how this feature works.
 
+
 ## One-to-many document key
 
 Each document in an index is uniquely identified by a document key. When no parsing mode is specified, and if there's no [explicit field mapping](search-indexer-field-mappings.md) in the indexer definition for the search document key, the blob indexer automatically maps the `metadata_storage_path property` as the document key. This default mapping ensures that each blob appears as a distinct search document, and it saves you the step of having to create this field mapping yourself (normally, only fields having identical names and types are automatically mapped).
@@ -136,6 +137,10 @@ Notice that each document contains the `id` field, which is defined as the `key`
 
 Similar to the previous example, this mapping doesn't result in four documents showing up in the index because the `id` field isn't unique _across blobs_. When this is the case, any json entry that specifies an `id` results in a merge on the existing document instead of an upload of a new document, and the state of the index reflects the latest read entry with the specified `id`.
 
+## Limitations
+
+When a document entry in the index is created from a line in a file, as explained in this article, deleting that line from the file does not automatically remove the corresponding entry from the index. To delete the document entry, you must manually submit a deletion request to the index using the [REST API deletion operation](addupdate-or-delete-documents.md).
+
 ## Next steps
 
 If you aren't already familiar with the basic structure and workflow of blob indexing, you should review [Indexing Azure Blob Storage with Azure AI Search](search-howto-index-json-blobs.md) first. For more information about parsing modes for different blob content types, review the following articles.