[Question] Weaviate Auto Schema: Why Are Properties Shared Across Collections?

Support
1

Question:

I have a question regarding Auto Schema in Weaviate.

Scenario:

• Auto Schema is enabled

  1. Create Collection A

  2. Add the following object:

{

“text”: “test”,

“files”: [

{

“path”: “path”,

“name”: “name”

}

]

}

  1. Create Collection B

  2. Add the following object:

{

“name”: “name”

}

  1. Create Collection C

  2. Try to add the following object, but an error occurs:

{

“files”: [“file”]

}

Observation:

Upon checking the schema, I noticed that properties were not created separately for each collection. Instead, the properties were generated based on the property types from Collection A and Collection B.

Question:

Why is this happening? How does Weaviate handle schema generation across multiple collections when Auto Schema is enabled?

Weaviate version : 1.26.1

2

Hey @mestanam,

Welcome to our community! Great to have you here.

I haven’t come across any issues with Auto Schema across multiple collections before when I tested :thinking:

Would you be able to share a small script or notebook that you tested locally? I can try reproducing it on my end with it and see what’s happening.