Azure搜索不再为Blob存储中的文档编制索引 [英] Azure search no longer indexing documents in blob storage

问题描述

直到几周前，我已经成功地为Azure blob存储中存储的文档设置了数据源，索引和索引器.文件正在按我的预期被编入索引.但是，现在不管我做什么，都不再对相同的文档建立索引.我已经尝试了几乎所有可能的组合，重新运行索引器，使用了不同的Blob存储，甚至删除并创建了新的Azure搜索服务，但无济于事.每当我运行索引器时，它只会告诉我成功处理0/0个文档.

Up until a couple of weeks ago, I was successfully setting up a data source, index and indexer for documents stored within Azure blob storage. The documents were being indexed as I expected. Now, however, no matter what I do, the same documents are no longer being indexed. I've tried pretty much all possible combinations, re-run the indexer, used different blob storage and even deleted and created a new Azure Search service, but all to no avail. Whenever I run the indexer it just tells me it has been a success with 0/0 documents.

我没有文件扩展名排除，在700个文档中只有大约20个将AzureSearch_Skip元数据设置为true.

I have no file extension exclusions, only about 20 out of 700 documents have AzureSearch_Skip metadata set to true.

我使用Azure门户的Azure搜索Web界面中的默认设置来设置数据源，索引器和索引.

I set up the data source, indexer and index using the default settings in the Azure Search web interface in the Azure portal.

如果Microsoft的任何人正在阅读，则Azure搜索服务称为KulaHub.

The Azure Search service is called KulaHub if anyone from Microsoft is reading.

Azure搜索在blob存储中为文档编制索引时是否存在问题?我知道这个问题没有细节，但我希望我能提供更多细节.

Is there an issue with Azure Search for indexing documents in blob storage? I know this question lacks specifics but I wish I could provide more details.

非常感谢

蒂姆

推荐答案

问题是索引器的批处理大小设置为0.请在门户中编辑索引器的属性，并将批处理大小"设置为某个合理的数字(10是默认设置，但是如果您的文档较小，则最好使用100-500之类的文件).

The issue is that your indexer batch size got set to 0. Please edit indexer properties in the portal and set the Batch Size to some reasonable number (10 is the default, but if your documents are small, something like 100-500 may be better).

这篇关于Azure搜索不再为Blob存储中的文档编制索引的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！