Increase Blob Indexer file size limits
The "Blob indexer: maximum characters of content extracted from a blob" limit seems rather restrictive, 32K for free, 64K for standard and 4MB for everything else. Plus when this limit is reached all you see in the azure portal is
[{ "key": null, "message": "Truncated extracted text to 32768 characters." }]
It'd be useful to know which documents are affected.
Luis Cabrera
shared this idea
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team
4 comments
-
Ben
commented
Agreed - not being able to index documents over 256MB seriously limits my ability to use Azure Search for my use case.
-
Rick Dorris
commented
I have about 10Gig of pdf documents that I need to index, but quite a few are larger than 4MB. Indexing only the first part of the document isn't an option. Does this mean Azure Search isn't the right tool for the job? Suggestions?
-
Walter
commented
Totally agree here, even at the Basic tier it would be great if document size had the same limits as the other standard tiers and that you just limited by number of documents or some other criteria for these lower prices. Our use case is less than 100 Microsoft Office documents and one index that gets accessed a few times a day but several of the documents are larger than 32K or even 64K meaning I have to go all the way to the lowest cost Standard tier and $250 a month for a few searches a day and that is not cost effective.
-
Mick Lang
commented
I think the bang for buck on Azure Search is a lot lower compared to the rest of the services on Azure. The Blob indexer: maximum blob size16Mb limit on the FREE and Basic tiers is also extremely limiting. The 128 limit on blob sizes for S1 also seems quite low for a service costing $300 a month.