#community-help

Issue with In-Place Schema Changes and Querying New Field

TLDR Ricardo faced issues querying a new field after in-place schema change. The problem was due to an older Python client, which was resolved by updating it.

Powered by Struct AI
4
5mo
Solved
Join the chat
Jun 22, 2023 (5 months ago)
Ricardo
Photo of md5-914a8b39b82fd99b8ecd985427660deb
Ricardo
03:20 AM
Hi all,
Since version 0.23
Schema changes: we now support fields to be added or dropped from a collection schema in-place.

We're trying to add a new field, and query by it. But it seems that we are not able to query by it. We can add it though, but then can't use it in a query. Is there any limitation on in-place changes?
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
03:25 AM
Could you confirm that you’re adding a field to the schema first before querying for it: https://typesense.org/docs/0.24.1/api/collections.html#update-or-alter-a-collection
Ricardo
Photo of md5-914a8b39b82fd99b8ecd985427660deb
Ricardo
04:15 AM
yeah, looks like it might be our python typesense client
05:12
Ricardo
05:12 AM
yeah we were using an older python library which didn't support the newer versions