0
votes

My azure blob indexer was running successfully up until 2-3 days ago for all documents in my storage. However now indexer seems like running successfully but with 0/0 documents. According to that previously posted question I've set Batch Size property, yet this didn't solve my issue. My indexer settings are:

Max failed items: -1
Max failed items per batch: -1
Batch size: 300

I have 176 blobs in my storage which have small sizes. Are there any other settings that should be considered in order to run indexer again?

I'm thinking that changing indexer's schedule might have caused to this problem (because it happened after i changed the running schedule frequency to custom) but I'm not so sure since i couldn't find anything to support this..

EDIT

After reading this tutorial, just to change last modified time, I updated my blob by right clicking -> properties -> save without changing anything. The indexer scanned this updated document but search index duplicated the file. Search Index is showing both previous and updated form of the same document now. I'm totally lost about the logic.

Thanks for any help

1
What is the definition of the index? Do both copies of the document show the same key value?Brendan Green
Sorry @BrendanGreen couldn't understand what do you mean by 'definition', what do you want me to provide ? No, updated doc's key starts with 'YQBI..', previous one starts with 'aHR0..'Serenay KIZILARSLAN
Your index will have a key (see docs.microsoft.com/en-us/azure/search/…). In whatever way you are using the indexer to read the document from blob storage, it appears to be getting a different key - hence you're getting a duplicate of the document inside the index.Brendan Green
@BrendanGreen yes, that was the problem. I've deleted all the blobs which have 'YQBI..' document key and then created a new index and indexer from scratch. It works fine now.Serenay KIZILARSLAN

1 Answers

0
votes

Are you referring to the same Azure Search service "KulaHub" as the linked previously posted question?