1. 10 Feb, 2015 2 commits
  2. 02 Feb, 2015 1 commit
    • mattcollier's avatar
      Update redis-cli.c · 7db39b7f
      mattcollier authored
      Code was adding '\n'  (line 521) to the end of NIL values exlusively making csv output inconsistent.  Removed '\n'
      7db39b7f
  3. 11 Dec, 2014 2 commits
  4. 09 Dec, 2014 1 commit
  5. 25 Nov, 2014 1 commit
  6. 30 Oct, 2014 1 commit
  7. 29 Oct, 2014 1 commit
  8. 26 Aug, 2014 9 commits
  9. 18 Jul, 2014 2 commits
  10. 26 Jun, 2014 1 commit
  11. 21 Jun, 2014 2 commits
  12. 06 Jun, 2014 1 commit
  13. 13 Mar, 2014 1 commit
  14. 05 Mar, 2014 1 commit
    • michael-grunder's avatar
      Improved bigkeys with progress, pipelining and summary · 23addbb5
      michael-grunder authored
      This commit reworks the redis-cli --bigkeys command to provide more
      information about our progress as well as output summary information
      when we're done.
      
       - We now show an approximate percentage completion as we go
       - Hiredis pipelining is used for TYPE and SIZE retreival
       - A summary of keyspace distribution and overall breakout at the end
      23addbb5
  15. 25 Feb, 2014 7 commits
  16. 22 Jan, 2014 2 commits
  17. 26 Sep, 2013 1 commit
  18. 04 Sep, 2013 1 commit
  19. 11 Jul, 2013 1 commit
  20. 03 Jul, 2013 2 commits
    • antirez's avatar
      redis-cli: introduced --pipe-timeout. · 1135e9fa
      antirez authored
      When in --pipe mode, after all the data transfer to the server is
      complete, now redis-cli waits at max the specified amount of
      seconds (30 by default, use 0 to wait forever) without receiving any
      reply at all from the server. After this time limit the operation is
      aborted with an error.
      
      That's related to issue #681.
      1135e9fa
    • antirez's avatar
      redis-cli --pipe: send final ECHO in a safer way. · fbb97c6b
      antirez authored
      If the protocol read from stdin happened to contain grabage (invalid
      random chars), in the previous implementation it was possible to end
      with something like:
      
      dksfjdksjflskfjl*2\r\n$4\r\nECHO....
      
      That is invalid as the *2 should start into a new line. Now we prefix
      the ECHO with a CRLF that has no effects on the server but prevents this
      issues most of the times.
      
      Of course if the offending wrong sequence is something like:
      
      $3248772349\r\n
      
      No one is going to save us as Redis will wait for data in the context of
      a big argument, so this fix does not cover all the cases.
      
      This partially fixes issue #681.
      fbb97c6b