Hi, is there any plan to re-configure key sizes in excess of 250? I know it was originally based on ASCII limits and standards, but that seems very antiquated as hardware get more powerful, and other products (velocity and built in .net cache?) support beyond this limit, Couchbase could break this limit?
The use case I have problem with is that SQL’s often become the key for caching, and some SQL could get lengthly. File paths for files could also become cache. The only 2 options I’ve seen are listed below, but both seem limited.
Hashing keys – dealing with collision is like hunting down a bug in camouflage. It’s not really an ideal fix.
Re-storing the cache key – others have suggested creating hash and using the hash to store a shortened version. This could work, except in some benchmarking, the (TCP) overhead of going back and fourth just to translate long to short keys is very noticable.
Does anyone have a better solution?
Some others have complained…