Major Description
Today, fts is storing the metadata like the index, node and plan definitions in a raw, uncompressed format within metakv.
Compressing the data before storing them into metakv would reduce the amount of data that the metakv has to process and hence potential performance improvements at scale.
But since this is a meta data format change, this will be a breaking change.
ie, it would have a implication on seamless upgrade and hence customers may need to start the cluster afresh with the new meta data format.
An interim (less breaking feature) could also be tested only for index definition meta data alone.