Hi guys, I want to check on what is the recommende...
# community-helpn
Nithin Saji
04/13/2021, 1:04 PMHi guys, I want to check on what is the recommended strategy for updating an existing collection ? Let's say we want to start faceting a new field in the documents? Deleting and recreating the collection with downtime seems too expensive.
k
Kishore Nallan
04/13/2021, 1:06 PM👋 As of now there is no way to modify the schema live, though that’s a very important todo item on our list. You can create another collection, index it in the background and use aliases to swap the live traffic over to that: https://typesense.org/docs/0.19.0/api/collection-alias.html#collection-alias
Kishore Nallan
04/13/2021, 1:12 PMIn the upcoming 0.20 release we are introducing automatic schema detection and support for regular expression in field names that will already help you work around this problem. For example you can define a field named
.*_facetKishore Nallan
04/13/2021, 1:13 PMWe already have a RC build for 0.20 that I can share if you are interested.
n
Nithin Saji
04/13/2021, 1:15 PMThanks Kishore, I am interested in trying it out.
k
Kishore Nallan
04/13/2021, 1:19 PMHere’s the docker image:
typesense/typesense:0.20.0.rc39{"name": ".*_str_facet", "type": "string", "facet": true}_str_facetKishore Nallan
04/13/2021, 1:20 PMThere is also full automatic type detection in the new version. WIP docs here for that: https://github.com/typesense/typesense-website/blob/775c22547727dee8bdae226a8dad90bb0e02df16/docs-site/content/0.20.0/api/collections.md#with[…]tion
n
Nithin Saji
04/13/2021, 1:28 PMThanks, I am already using the rc, will give this a try.
Nithin Saji
04/13/2021, 2:01 PMIs it possible to search or facet using nested fields when using auto ?
k
Kishore Nallan
04/13/2021, 2:02 PMWe don’t support indexing and searching on nested fields. You need to flatten all nested fields to top-level fields using a
customer.name