Azure搜索索引器和Blob容器中的最大块大小 [英] Azure search Indexer and Maximum block size in blob container
问题描述
我对Blob存储和Azure搜索有疑问.我正在使用基于 的Azure搜索服务blob容器中的可用文件.
I have question related to Blob Storage and Azure Search. I am using azure search service based on the files available in the blob container.
根据Blob存储描述，最大块大小为100MB，但是如果我们上传的文件大小最大为1GB或更大，它将如何管理更大的文件?它会分割并创建100MB的多个文件吗?
According to the blob storage description, maximum block size 100MB but if we are uploading the files upto size 1GB or more, how does it manage the bigger files? does it divide and create the 100MB multiple files?
第二，Azure搜索索引器可以提取的最大文件大小是多少?因为文件较大，我们无法创建索引器.
Secondly, what is maximum file size that azure search indexer can extract? because with bigger file size we can't create the indexer.
感谢您的帮助.
关于
Gohar
推荐答案
Hi Gohar,Regarding the first one, refer to https://docs.microsoft.com/en-us/rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs
"存储客户端默认最大128 MB单个blob上传，可使用 BlobRequestOptions 对象.当块Blob上传大于此属性中的值时，存储客户端会将文件分成块.您可以使用 BlobRequestOptions 对象.
"Storage clients default to a 128 MB maximum single blob upload, settable using the SingleBlobUploadThresholdInBytes property of the BlobRequestOptions object. When a block blob upload is larger than the value in this property, storage clients break the file into blocks. You can set the number of threads used to upload the blocks in parallel on a per-request basis using the ParallelOperationThreadCount property of the BlobRequestOptions object.
将块上载到存储帐户中的Blob时，该块与指定的块Blob相关联，但是在您提交包含新块ID的块列表之前，该块不会成为该Blob的一部分.新块保持未提交状态 直到明确承诺或丢弃它们为止.编写块不会更新现有Blob的最后修改时间.
When you upload a block to a blob in your storage account, it is associated with the specified block blob, but it does not become part of the blob until you commit a list of blocks that includes the new block's ID. New blocks remain in an uncommitted state until they are specifically committed or discarded. Writing a block does not update the last modified time of an existing blob.
块Blob包含有助于您通过网络管理大型文件的功能.使用块Blob，您可以并行上传多个块，以减少上传时间.每个块都可以包含MD5哈希值以验证传输，因此您可以跟踪上传进度 然后根据需要重新发送代码块.您可以按任何顺序上传块，并在最后的阻止列表提交步骤中确定其顺序.您还可以上传新块，以替换具有相同块ID的现有未提交块.您有一个星期要提交 块被丢弃之前，先将其删除.当发生阻止列表承诺操作但不包括所有未提交的块时，也会将所有未提交的块丢弃. "
Block blobs include features that help you manage large files over networks. With a block blob, you can upload multiple blocks in parallel to decrease upload time. Each block can include an MD5 hash to verify the transfer, so you can track upload progress and re-send blocks as needed. You can upload blocks in any order, and determine their sequence in the final block list commitment step. You can also upload a new block to replace an existing uncommitted block of the same block ID. You have one week to commit blocks to a blob before they are discarded. All uncommitted blocks are also discarded when a block list commitment operation occurs but does not include them. "
就第二个而言，限制列在 https://docs.microsoft.com/zh-CN/azure/search/search-limits-quotas-capacity
As far as the second one goes, the limits are listed at https://docs.microsoft.com/en-us/azure/search/search-limits-quotas-capacity
hth
Marcin
这篇关于Azure搜索索引器和Blob容器中的最大块大小的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
