There is no way to update a collection schema?
# community-helps
Stefan Hesse
04/06/2021, 12:08 PMThere is no way to update a collection schema?
k
Kishore Nallan
04/06/2021, 12:16 PM@Stefan Hesse We don't have a way to do that at the moment, but in 0.20 (for which we already have a release candidate available), we support automatic schema detection which might help in some cases (for e.g. if new fields get added, they will get indexed automatically).
However, schema update is on our roadmap.
r
Rishabh Agrawal
04/14/2021, 10:28 PMis there any workaround for this ? also query_by doesn't work for fields which are not mentioned while creating collection
j
Jason Bosco
04/14/2021, 10:31 PMHi @Rishabh Agrawal For now the work-around is to create a new collection with the new schema and re-index the data. To make this zero-downtime, you want to setup a collection alias and use that alias in your application.
So for eg: if you have a set of books, you'd create a collection called
books_<current_timetsamp>_1booksbooksbooks_<current_timetsamp>_2booksbooks_<current_timetsamp>_2Jason Bosco
04/14/2021, 10:32 PMalso query_by doesn't work for fields which are not mentioned while creating collectionThis is by design. Only fields mentioned in the schema when creating the collection are indexed & searchable fields. All others are just stored on disk and returned with the results. So to be able to use a field in queryBy, it has to be specified in the collection schema
r
Rishabh Agrawal
04/14/2021, 10:34 PMokay, thanks for the response, let me try
Rishabh Agrawal
04/14/2021, 10:52 PMwhile creating a new collection is there a way i can define my own field as an id ? for eg. defining studentRollNumber as an id. otherwise typesense will create the id of it's own
j
Jason Bosco
04/14/2021, 11:53 PMUnfortunately no, the ID field needs to be called
idr
Rishabh Agrawal
04/15/2021, 7:37 AMok