Secondary Index Migration in YugabyteDB

YugabyteDB has a feature for strongly consistent secondary indexes, but modifying existing indexes is not currently possible through the Yugabyte CQL API. However, there are ways to achieve this without taking downtime or restarting applications. One approach is to drop and recreate the index with the desired columns, which can take time and potentially affect application performance. Another approach is to create a new index first, including additional columns using the INCLUDE clause, and then dropping the old index once it has backfilled. This second approach avoids potential issues with disk space usage and write penalties, but still requires testing in a lower environment before production deployment.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.