Skip to content

Weaviate destination connector: record_id property required on collections #372

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Dec 6, 2024
Merged

Weaviate destination connector: record_id property required on collections #372

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 20 additions & 3 deletions snippets/general-shared-text/weaviate.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,23 @@
allowfullscreen
></iframe>

Weaviate requires the collection to have a data schema before you add data. However, you don't have to create a data schema manually.
If you don't provide one, Weaviate generates a schema based on the incoming data.
Weaviate requires the collection to have a data schema before you add data. At minimum, this schema must contain the `record_id` property, as follows:

However, if you have specific schema requirements, you can create the schema manually.
```json
{
"class": "Elements",
"properties": [
{
"name": "record_id",
"dataType": ["text"]
}
]
}
```

Weaviate generates any additional properties based on the incoming data.

If you have specific schema requirements, you can define the schema manually.
Unstructured cannot provide a schema that is guaranteed to work for everyone in all circumstances.
This is because these schemas will vary based on
your source files' types; how you want Unstructured to partition, chunk, and generate embeddings;
Expand All @@ -38,6 +51,10 @@ You can adapt the following collection schema example for your own specific sche
{
"class": "Elements",
"properties": [
{
"name": "record_id",
"dataType": ["text"]
},
{
"name": "element_id",
"dataType": ["text"]
Expand Down