https://<cluster-id>.<cluster-type>.<cloud-provider>-<region>.cloud.zilliz.com
.
Get the cluster’s public endpoint.
element_id
, embeddings
, and record_id
, as follows:
Field Name | Field Type | Max Length | Dimension | Index | Metric Type |
---|---|---|---|---|---|
element_id (primary key field) | VARCHAR | 200 | — | — | — |
embeddings (vector field) | FLOAT_VECTOR | — | 3072 | Yes (Checked) | Cosine |
record_id | VARCHAR | 200 | — | — | — |
https://
, followed by instance’s GRPC host, followed by a colon and the GRPC port.
This takes the format of https://<host>:<port>
.
Get the instance’s GRPC host and GRPC port.ibmlhapikey
.
The password for Milvus on IBM watsonx.data is in the form of an IBM Cloud user API key.
Get the user API key.element_id
, embeddings
, and record_id
, as follows. This example code demonstrates the use of the
Python SDK for Milvus to create a collection with this minimum viable schema,
targeting Milvus on IBM watsonx.data. For the connections.connect
arguments to connect to other types of Milvus deployments, see your Milvus provider’s documentation:
MILVUS_URI
- The Milvus instance’s URI, represented by --uri
(CLI) or uri
(Python).MILVUS_USER
and MILVUS_PASSWORD
, or MILVUS_TOKEN
- The username and password, or token, to access the instance. This is represented by --user
and --password
, or --token
(CLI); or user
and password
, or token
(Python).MILVUS_DB
- The database’s name, represented by --db-name
(CLI) or db_name
(Python).MILVUS_COLLECTION
- The collection’s name, represented by --collection-name
(CLI) or collection_name
(Python).MILVUS_FIELDS_TO_INCLUDE
- A list of fields to include a comma-separated list (CLI) or an array of strings (Python), represented by --field-to-include
(CLI) or fields_to_include
(Python).metadata
field’s child fields directly into the output, include --flatten-metadata
(CLI) or flatten_metadata=True
(Python). This is the default if not specified.metadata
field with its child fields intact in the output, include --no-flatten-metadata
(CLI) or flatten_metadata=False
(Python).--partition-by-api
option (CLI) or partition_by_api
(Python) parameter to specify where files are processed:
--partition-by-api
(CLI) or partition_by_api
(Python), or explicitly specify partition_by_api=False
(Python).
Local file processing does not use an Unstructured API key or API URL, so you can also omit the following, if they appear:
--api-key $UNSTRUCTURED_API_KEY
(CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY")
(Python)--partition-endpoint $UNSTRUCTURED_API_URL
(CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL")
(Python)UNSTRUCTURED_API_KEY
and UNSTRUCTURED_API_URL
--partition-by-api
(CLI) or partition_by_api=True
(Python).
Unstructured also requires an Unstructured API key and API URL, by adding the following:
--api-key $UNSTRUCTURED_API_KEY
(CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY")
(Python)--partition-endpoint $UNSTRUCTURED_API_URL
(CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL")
(Python)UNSTRUCTURED_API_KEY
and UNSTRUCTURED_API_URL
, representing your API key and API URL, respectively.https://api.unstructuredapp.io/general/v0/general
, which is the API URL for the Unstructured Partition Endpoint. However, you should always use the URL that was provided to you when your Unstructured account was created. If you do not have this URL, contact Unstructured Sales at sales@unstructured.io.If you do not have an API key, get one now.If the Unstructured API is self-hosted, the process
for generating Unstructured API keys, and the Unstructured API URL that you use, are different.
For details, contact Unstructured Sales at
sales@unstructured.io.