{"action":"created","issue":{"url":"https://api.github.com/repos/antirez/redis/issues/2325","labels_url":"https://api.github.com/repos/antirez/redis/issues/2325/labels{/name}","comments_url":"https://api.github.com/repos/antirez/redis/issues/2325/comments","events_url":"https://api.github.com/repos/antirez/redis/issues/2325/events","html_url":"https://github.com/antirez/redis/issues/2325","id":55682173,"number":2325,"title":"Simple options still missing","user":{"login":"Robot7","id":10731946,"avatar_url":"https://avatars.githubusercontent.com/u/10731946?v=3","gravatar_id":"","url":"https://api.github.com/users/Robot7","html_url":"https://github.com/Robot7","followers_url":"https://api.github.com/users/Robot7/followers","following_url":"https://api.github.com/users/Robot7/following{/other_user}","gists_url":"https://api.github.com/users/Robot7/gists{/gist_id}","starred_url":"https://api.github.com/users/Robot7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Robot7/subscriptions","organizations_url":"https://api.github.com/users/Robot7/orgs","repos_url":"https://api.github.com/users/Robot7/repos","events_url":"https://api.github.com/users/Robot7/events{/privacy}","received_events_url":"https://api.github.com/users/Robot7/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-01-27T22:12:55Z","updated_at":"2015-01-28T03:58:47Z","closed_at":null,"body":"It has been a year or two, many of us are still waiting for simple options such as zadd only if exists.\r\n\r\nFrom the average user's point of view, Redis's progress has simply stalled. I can't believe Redis spent a year on developing replication, a feature most people won't even use. In the real world, users who've reached the point where their data won't fit a 32gb non ECC server, or exceeds 256G/512G/1T on a ECC server, should be skilled enough to handle their own sharding and mirroring, or at the very least have the revenue to hire people to handle it.\r\n\r\nAnd if I am a big player, I am not going to trust my data on Redis's replication, I'll have my own solution, replication takes years to develop, is Redis going to stall a few more years just to replicate itself?\r\n\r\nI know what the Redis team is going to say, you can do everything in lua, but it is simply not efficient. Instead of a simple command, we have to cache a script, run the script, then catch not only the normal error, but also the error of a missing script cache just incase the script was not loaded. and if so, load the script and send the script command again.\r\n\r\nI don't understand why Redis isn't focusing on strengthening the basics, for example, make sure every simple add/remove commands are covered with \"add if exists\" \"add if not exists\" \"remove if exists\". These simple options would make Redis much more useful, especially to new users with no lua background.\r\n\r\nThese options are not hard to implement either, won't take more than 50 lines of C codes each. Yet, Redis spent years on some web 2.0 buzz word, PostgreSQL had a huge team and they took years to master their replication, it took them till version 9.3 to have proper reliable diskless replication mechanisms.\r\n\r\nI am done asking for features here, have fun wasting years chasing after some web 2.0 buzz word, trying to turn Redis into something it isn't, while missing all the chances to become a fully complete toolbox.\r\n"},"comment":{"url":"https://api.github.com/repos/antirez/redis/issues/comments/71777457","html_url":"https://github.com/antirez/redis/issues/2325#issuecomment-71777457","issue_url":"https://api.github.com/repos/antirez/redis/issues/2325","id":71777457,"user":{"login":"michael-grunder","id":468149,"avatar_url":"https://avatars.githubusercontent.com/u/468149?v=3","gravatar_id":"","url":"https://api.github.com/users/michael-grunder","html_url":"https://github.com/michael-grunder","followers_url":"https://api.github.com/users/michael-grunder/followers","following_url":"https://api.github.com/users/michael-grunder/following{/other_user}","gists_url":"https://api.github.com/users/michael-grunder/gists{/gist_id}","starred_url":"https://api.github.com/users/michael-grunder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/michael-grunder/subscriptions","organizations_url":"https://api.github.com/users/michael-grunder/orgs","repos_url":"https://api.github.com/users/michael-grunder/repos","events_url":"https://api.github.com/users/michael-grunder/events{/privacy}","received_events_url":"https://api.github.com/users/michael-grunder/received_events","type":"User","site_admin":false},"created_at":"2015-01-28T03:58:47Z","updated_at":"2015-01-28T03:58:47Z","body":"@mattsta I concur with @bbroerman30 not that you need any assurance.  I mean for crying out loud, Redis is free and open source.  Anyone can fork it and implement all manner of custom behavior that they like.  OP is simultaneously complaining that these specific features haven't been implemented whilst talking about how easy they are to implement.  \r\n\r\n@Robot7 Then implement them and move on.  If you think the commands are of generic use to the wider community, by all means submit a pull request.  It may or may not be merged, but if not, run your custom fork that has the functionality you need.\r\n\r\nTL;DR:  Trolls gonna troll.\r\n\r\n"}}