Azure Indexer error....Invalid document key
Azure Indexer Error.
I have been running the Azure Indexer on a blob storage container that contains pdfs. The indexer Indexed more than 7000 blobs successfully then started throwing these errors for any additional documents.
{
"key": "https://yoursiteurl/169292.pdf",
"errorMessage": "Invalid document key: 'https://yoursiteurl/processed-documents/169292.pdf'. Keys can only contain letters, digits, underscore (_), dash (-), or equal sign (=). Please see https://docs.microsoft.com/azure/search/search-howto-indexing-azure-blob-storage#DocumentKeys"
}
I see nothing wrong with the document itself and am wondering if this has anything to do with keys.
Here is index metadata:
Here is the blob metadata:
I have been running the Azure Indexer on a blob storage container that contains pdfs. The indexer Indexed more than 7000 blobs successfully then started throwing these errors for any additional documents.
{
"key": "https://yoursiteurl/169292.pdf",
"errorMessage": "Invalid document key: 'https://yoursiteurl/processed-documents/169292.pdf'. Keys can only contain letters, digits, underscore (_), dash (-), or equal sign (=). Please see https://docs.microsoft.com/azure/search/search-howto-indexing-azure-blob-storage#DocumentKeys"
}
I see nothing wrong with the document itself and am wondering if this has anything to do with keys.
Here is index metadata:
Here is the blob metadata:
ste5an
Well, without testing: the slash is neither a letter, a digit, an underscore (_), a dash (-), nor an equal sign (=).
ASKER
But where is it picking up the slash from? Which field? Sorry i dont understand.
From the key, seems that you cannot use the media storage path as key.
ASKER
Also i didnt check base 64 encoding on the indexer
Do you recommend a different type of field for the index primary key? When you create a new index it uses metadata_storage_path as the default option.
Maybe some generic id or metadata_storage_name
But i definately did not have base 64 encoding checked. I tried updating the indexers base 64 encoding property through postman rest api but it wont let me.
Do you recommend a different type of field for the index primary key? When you create a new index it uses metadata_storage_path as the default option.
Maybe some generic id or metadata_storage_name
But i definately did not have base 64 encoding checked. I tried updating the indexers base 64 encoding property through postman rest api but it wont let me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.