Hi all, I’d like to open a discussion on adding *composite key support* in the ResilientDB storage layer to improve secondary attribute indexing.
Currently, applications that need secondary lookups either: - Fetch all values and filter in memory, or - Export and sync data to an external datastore. This creates inefficiencies and complexity for applications using ResilientDB as a KV or document store (e.g., ResLens, ResCanvas, Coinsensus). Composite keys provide a lightweight solution, enabling efficient secondary lookups directly in the storage layer, similar to MyRocks (MySQL) and Hyperledger Fabric. We’ve drafted a detailed proposal (background, problem statement, solution, trade-offs, and API changes) in the following GitHub issue: GitHub Issue: https://github.com/apache/incubator-resilientdb/issues/180 Please share your thoughts on this approach. If the community agrees, we can move forward with a design doc and implementation plan. Best, Harish Krishnakumar PPMC , Apache ResilientDB
