Noticed today if you delete an index which is still being restored (offered way to cancel an index restore) BlobContainer still keeps reading incoming stream.
If you have very large index, you can not start another restore operation before waiting it to complete even result will be simply nothing.
I experience this with S3 but probably it is a case for all other restore options.
Hi,
Noticed today if you delete an index which is still being restored (offered way to cancel an index restore) BlobContainer still keeps reading incoming stream.
If you have very large index, you can not start another restore operation before waiting it to complete even result will be simply nothing.
I experience this with S3 but probably it is a case for all other restore options.