milvus-io
[Enhancement]: Refine the document of import
Is there an existing issue for this?
- [X] I have searched the existing issues
What would you like to be added?
Upon reviewing the document on data import found at https://milvus.io/docs/import_data.md, it appears that there's room for clarification regarding the workings of Milvus and the preparation of files.
To enhance clarity and usability, I propose the following refinements:
-
Migration of Local Storage Information: The section discussing local storage considerations should be relocated to the documentation for Lite Milvus. A reference to this section can then be provided in the main document.
-
Clear Description of Import Lifecycle: A diagram should be included to depict the import lifecycle clearly. This diagram should illustrate the key components involved, such as S3 or MinIO.
-
Inclusion of Working Examples: Practical examples should be provided to demonstrate the process of uploading files to S3 or MinIO and how to specify the file path (S3 key) variable when invoking the import API.
By implementing these refinements, users will have a more straightforward understanding of how Milvus operates and how to effectively prepare and import their data.
Why is this needed?
No response
Anything else?
No response
/assign @topikachu @bigsheeper maybe you can work together on that?
Of course.
@topikachu And thank you very much for your suggestions. Your feedback is greatly helpful in enhancing the user experience.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
@bigsheeper: Reopened this issue.
In response to this:
/reopen
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.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.