Is your feature request related to a problem? Please describe.
Secondary indices are very powerful and the main advantage against classical key-value-store and multi-column databases and I am happy, that it is part of Tigris, but once you have created a collection, you cannot add any later via implicit code migration.
But luckily it is possible in Tigris to do via Web Console, but due to automated pipeline and multi staging, I need to have to add or remove secondary indicies via client API within migration scripts.
Describe the solution you'd like
In the typescript client I would like to have a function to add and remove secondary indices on collection fields. I am aware of that each entry in the collection needs to processed for adding into the new index.
Describe alternatives you've considered
I see no alternatives (rather then implicit or explicit addition and removal of a secondary index), as of new indices can be required within product development progress continuously and a full copy of a whole collection with data and branches is not a feasible workaround.
Is your feature request related to a problem? Please describe. Secondary indices are very powerful and the main advantage against classical key-value-store and multi-column databases and I am happy, that it is part of Tigris, but once you have created a collection, you cannot add any later via implicit code migration. But luckily it is possible in Tigris to do via Web Console, but due to automated pipeline and multi staging, I need to have to add or remove secondary indicies via client API within migration scripts.
Describe the solution you'd like In the typescript client I would like to have a function to add and remove secondary indices on collection fields. I am aware of that each entry in the collection needs to processed for adding into the new index.
Describe alternatives you've considered I see no alternatives (rather then implicit or explicit addition and removal of a secondary index), as of new indices can be required within product development progress continuously and a full copy of a whole collection with data and branches is not a feasible workaround.
Additional context No additional context.