[Bug]: Bulk Insert failed during Milvus restore with GCS native buckets using Milvus Backup tool

[gifi-siby]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Perform a Milvus restore operation using the Milvus Backup tool to restore data to a Milvus instance associated with a GCS native bucket. Below error is found:
workerpool: execute job no binlog to import, input=[paths:"nativemill/BackupMilvus864/flavorBack1/binlogs/insert_log/453580537997566884/453580537997566885/453580537997766901/" paths:"" ]: invalid parameter

Expected Behavior

Restore operation using the MilvusBack tool should be success without any error.

Steps To Reproduce

1. Create a backup using MilvusBackup tool
2. Restore the data to milvus associated with GCP native bucket

Milvus Log

No response

Anything else?

As part of BulkInsert, ListObjects function of GCPNativeObjectStorage is called to list all the folders and files inside a certain path (inside backupPath/binlogs/insert_log/collectionID/partitionID/segmentID/groupID).
Only end files were returned from ListObjects (folder-like objects are skipped) and thus empty array of string was returned (thus no binlogs were found).
This issue is found as part of the MilvusBackup tool enhancement:
Enhancement task: #444
PR raised: #495

[yanliang567]

/assign @huanghaoyuanhhy
/unassign

[sre-ci-robot]

@yanliang567: GitHub didn't allow me to assign the following users: huanghaoyuanhhy.

Note that only milvus-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @huanghaoyuanhhy
/unassign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[gifi-siby]

/assign @gifi-siby