Currently, in cbft 0.0.3, to rebuild an index from scratch, the user clicks on 'edit' of an index definition, and without making any changes (especially, keeping the same index name), the user clicks on the 'Update Index' button.
This causes a new index UUID to be assigned to the effectively unchanged index definition, so the whole backend gearworks of shutting down the old pindexes and bringing up brand new pindexes automatically swings into motion across the cbft cluster.
Kinda cool behind the scenes, the the front of the store needs a better UI on this.
Currently, in cbft 0.0.3, to rebuild an index from scratch, the user clicks on 'edit' of an index definition, and without making any changes (especially, keeping the same index name), the user clicks on the 'Update Index' button.
This causes a new index UUID to be assigned to the effectively unchanged index definition, so the whole backend gearworks of shutting down the old pindexes and bringing up brand new pindexes automatically swings into motion across the cbft cluster.
Kinda cool behind the scenes, the the front of the store needs a better UI on this.