Why does TokuDB impose a limit of 64 keys per table?

Question

Why does TokuDB impose a limit of 64 keys per table by default, while systems like Elasticsearch allow any number of fields to be indexed (limited only by available resources)?

Answer 1

Short answer, because at some point you simply need to put limits in your software. TokuDB is a storage engine for MySQL which supports far more operations than Elasticsearch, so there are trade-offs to be considered. Since TokuDB is open source I'd imagine you could find this value somewhere in the source code and raise it to something higher, compile, test, and deploy.

Answer 2

This is a MySQL limit, grep MAX_INDEXES