1. 09 Jul, 2014 29 commits
  2. 02 Jul, 2014 1 commit
  3. 30 Jun, 2014 2 commits
  4. 27 Jun, 2014 8 commits
    • antirez's avatar
      COMMAND COUNT subcommand added. · 63feb93a
      antirez authored
      63feb93a
    • antirez's avatar
      COMMAND: fix argument parsing. · 0a6649a7
      antirez authored
      This fixes detection of wrong subcommand (that resulted in the default
      all-commands output instead) and allows COMMAND INFO to be called
      without arguments (resulting into an empty array) which is useful in
      programmtically generated calls like the following (in Ruby):
      
          redis.commands("command","info",*mycommands)
      
      Note: mycommands may be empty.
      0a6649a7
    • antirez's avatar
      COMMANDS command renamed COMMAND. · 53377f8c
      antirez authored
      53377f8c
    • antirez's avatar
      COMMANDS command: remove static + aesthetic changes. · f3efd529
      antirez authored
      Static was removed since it is needed in order to get symbols in stack
      traces. Minor changes in the source code were operated to make it more
      similar to the existing Redis code base.
      f3efd529
    • Matt Stancliff's avatar
      Cluster: Add COMMANDS command · fdc5dbd5
      Matt Stancliff authored
      COMMANDS returns a nested multibulk reply for each
      command in the command table.  The reply for each
      command contains:
        - command name
        - arity
        - array of command flags
        - start key position
        - end key position
        - key offset step
        - optional: if the keys are not deterministic and
          Redis uses an internal key evaluation function,
          the 6th field appears and is defined as a status
          reply of: REQUIRES ARGUMENT PARSING
      
      Cluster clients need to know where the keys are in each
      command to implement proper routing to cluster nodes.
      
      Redis commands can have multiple keys, keys at offset steps, or other
      issues where you can't always assume the first element after
      the command name is the cluster routing key.
      
      Using the information exposed by COMMANDS, client implementations
      can have live, accurate key extraction details for all commands.
      
      Also implements COMMANDS INFO [commands...] to return only a
      specific set of commands instead of all 160+ commands live in Redis.
      fdc5dbd5
    • antirez's avatar
      Remove infinite loop from PSYNC test. · afe949ef
      antirez authored
      Added for debugging and forgot there.
      afe949ef
    • antirez's avatar
      Test: hopefully more robust PSYNC test. · 1066fed7
      antirez authored
      This is supposed to fix issue #1417, but we'll know if this is enough
      only after a couple of runs of the CI test without false positives.
      1066fed7
    • Matt Stancliff's avatar
      Allow __powerpc__ to define HAVE_ATOMIC too · cd4f0dc7
      Matt Stancliff authored
      From mailing list post https://groups.google.com/forum/#!topic/redis-db/D3k7KmJmYgM
      
      In the file “config.h”, the definition HAVE_ATOMIC is used to indicate
      if an architecture on which redis is implemented supports atomic
      synchronization primitives.  Powerpc  supports atomic synchronization
      primitives, however, it is not listed as one of the architectures
      supported in config.h. This patch  adds the __powerpc__ to the list of
      architectures supporting these primitives. The improvement of redis
      due to the atomic synchronization on powerpc is significant,
      around 30% to 40%, over the default implementation using pthreads.
      
      This proposal adds __powerpc__ to the list of architectures designated
      to support atomic builtins.
      cd4f0dc7