I use Redis' Lua scripting pretty heavily, because it's amazingly useful, and here are the features I would like most:
1. LuaJIT. The extra speed would open up a lot of new possibilities for doing fancy things with Lua scripting. A big enough quantitative difference in speed is a qualitative difference.
2. The ability to add on third-party libraries. The modules that come out of the box are great, but there's a lot of other good code out there.
3. More convenient ways of writing a logging statement than redis.log(redis.LOG_DEBUG, "Hello, world!"). I end up needing to look up the syntax for that one more often than I'd like to admit.
Finally, a request that doesn't involve Lua: several times, it would have been very convenient to be able to iterate through all the keys in a Redis database in constant space. The "KEYS *" command doesn't stream keys; it buffers them up, which may explode on large databases. My alternate approach was to parse the RDB dump file offline, but that's tricky and kind of slow with the tools that exist now.
Have you tried just replacing redis' Lua dependency with LuaJIT yourself? LuaJIT 2.0 should be a drop-in replacement for Lua 5.1, it has the same headers and even builds the same way.
What kind of things are you using Lua scripting for? I've not had a need to solve any problems using it yet, so I'm really interested in hearing about case-studies in the wild.
1. LuaJIT. The extra speed would open up a lot of new possibilities for doing fancy things with Lua scripting. A big enough quantitative difference in speed is a qualitative difference.
2. The ability to add on third-party libraries. The modules that come out of the box are great, but there's a lot of other good code out there.
3. More convenient ways of writing a logging statement than redis.log(redis.LOG_DEBUG, "Hello, world!"). I end up needing to look up the syntax for that one more often than I'd like to admit.
Finally, a request that doesn't involve Lua: several times, it would have been very convenient to be able to iterate through all the keys in a Redis database in constant space. The "KEYS *" command doesn't stream keys; it buffers them up, which may explode on large databases. My alternate approach was to parse the RDB dump file offline, but that's tricky and kind of slow with the tools that exist now.