Settings and activity
2 results found
-
12 votes
We’re currently gathering additional feedback on this feedback and we're exploring a potential fix. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
An error occurred while saving the comment
Vipul Shrivastva
supported this idea
·
-
19 votes
Vipul Shrivastva
supported this idea
·
An error occurred while saving the comment
Vipul Shrivastva
commented
This feature/fix is quite important, and it would be beneficial to include it in the upcoming releases.
We are also impacted by this behavior. The purge should only remove content data, not the underlying schema or storage container. Deleting the schema causes subsequent indexing attempts to fail with index not found, even though the API returns a success response. This makes the purge operation unsafe for production use. We strongly support changing the purge behavior so that only content is removed, while the schema remains intact.