We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think it's related to #5
Hi, I'm trying to perform a data migration between two milvus collections using spark-milvus
The data is split into several partitions, When I'm reading the data, I'm able to pass MILVUS_PARTITION_NAME param, (as it was recently added
MilvusOptions.MILVUS_HOST -> host, MilvusOptions.MILVUS_PORT -> port.toString, MilvusOptions.MILVUS_COLLECTION_NAME -> collectionName, MilvusOptions.MILVUS_PARTITION_NAME -> partitionName, MilvusOptions.MILVUS_BUCKET -> bucketName, MilvusOptions.MILVUS_ROOTPATH -> rootPath, MilvusOptions.MILVUS_FS -> fs, MilvusOptions.MILVUS_STORAGE_ENDPOINT -> minioEndpoint, MilvusOptions.MILVUS_STORAGE_USER -> minioAK, MilvusOptions.MILVUS_STORAGE_PASSWORD -> minioSK ) val milvusOptions = new MilvusOptions( new CaseInsensitiveStringMap(properties.asJava) ) val collectionDF = MilvusUtils.readMilvusCollection(spark, milvusOptions)
however whole collection is being loaded into a dataframe.
Can you please provide guidance what has to be done to fix this behavior ? I don't have expertise on milvus-binlog format.
The text was updated successfully, but these errors were encountered:
@meako689 Yes read by partition is not supported yet. We can support it soon
Sorry, something went wrong.
No branches or pull requests
I think it's related to #5
Hi, I'm trying to perform a data migration between two milvus collections using spark-milvus
The data is split into several partitions,
When I'm reading the data, I'm able to pass MILVUS_PARTITION_NAME param, (as it was recently added
however whole collection is being loaded into a dataframe.
Can you please provide guidance what has to be done to fix this behavior ? I don't have expertise on milvus-binlog format.
The text was updated successfully, but these errors were encountered: