-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pre run case error: The specified key does not exist for Search Performance Test (100M Dataset, 768 Dim) on Milvus Standalone #267
Comments
@XuanYang-cn looks like some problem with the data download, please help ~ |
Any fix to this yet? |
XuanYang-cn
added a commit
to XuanYang-cn/VectorDBBench
that referenced
this issue
Mar 4, 2024
Fixes: zilliztech#267, zilliztech#275, zilliztech#285 Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn
added a commit
to XuanYang-cn/VectorDBBench
that referenced
this issue
Mar 4, 2024
Fixes: zilliztech#267, zilliztech#275, zilliztech#285 Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn
added a commit
to XuanYang-cn/VectorDBBench
that referenced
this issue
Mar 4, 2024
Fixes: zilliztech#267, zilliztech#275, zilliztech#285 Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn
added a commit
to XuanYang-cn/VectorDBBench
that referenced
this issue
Mar 5, 2024
Fixes: zilliztech#267, zilliztech#275, zilliztech#285 Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn
added a commit
to XuanYang-cn/VectorDBBench
that referenced
this issue
Mar 5, 2024
Fixes: zilliztech#267, zilliztech#275, zilliztech#285 Signed-off-by: yangxuan <xuan.yang@zilliz.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. I was trying to run a test run for Milvus Standalone with the Search Performance Test (100M Dataset, 768 Dim). However, I got the following output with an error of specified key does not exist:
Currently starting up the Milvus Standalone through Docker Compose with the following docker-compose.yml:
The text was updated successfully, but these errors were encountered: