Hi Guys, A question about auto schema detection. Suppose using a CMS if i have a facet - lets say “facet_a” is later renamed in the CMS to “facet_b” facet_a remains in schema for that collection even though it has been renamed now to “facet_b” So collection would have both facet_a and facet_b in it’s schema as a facet. Would it be better to drop the collection and re-index (something i would like to avoid) or can we leave facet_a in the schema without worrying about it.

As long it's an optional field, no harm leaving it in the collection schema. We will support schema updates in the near future, and this can be cleaned up then.

Ok looking forward to that update - i’ll stay tuned. Thanks Kishore