scala-redis
scala-redis copied to clipboard
debasishg
A scala library for connecting to a redis server, or a cluster of redis nodes using consistent hashing on the client side.
Am I missing the documentation on connecting to password enabled Redis instances or is the documentation missing it? For example the RedisCloud Paas instance on Heroku needs something like "redis://rediscloud:[password-string...
HyperLogLog structures were added in Redis 2.8.9 and it would be nice to have them support. Pull request to follow
I do: lazy val nodes = Array(ClusterNode("node0", "localhost", 6379),ClusterNode("node1", "localhost", 6380)) lazy val r = new RedisCluster(new WrappedArray.ofRef(nodes): _*) { val keyTag = Some(RegexKeyTag) } then the examples work, but...
following is my build.scala name := "testRedis" version := "1.0" libraryDependencies += "org.scalatest" % "scalatest_2.10" % "2.1.0" % "test" libraryDependencies +="net.debasishg" % "redisclient_2.10" % "2.12" I see class not found...
Would be nice to be able to pass a List to mget :)
[2014-07-01 19:40:17] NOAUTH Authentication required. [akka.actor.OneForOneStrategy] java.lang.Exception: NOAUTH Authentication required. at com.redis.Reply$$anonfun$6.applyOrElse(RedisProtocol.scala:93) ~[redisclient_2.10-2.13.jar:2.13] at com.redis.Reply$$anonfun$6.applyOrElse(RedisProtocol.scala:92) ~[redisclient_2.10-2.13.jar:2.13] at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:33) ~[scala-library-2.10.4.jar:na] at com.redis.Reply$$anonfun$4.applyOrElse(RedisProtocol.scala:62) ~[redisclient_2.10-2.13.jar:2.13] at com.redis.Reply$$anonfun$4.applyOrElse(RedisProtocol.scala:62) ~[redisclient_2.10-2.13.jar:2.13] at scala.PartialFunction$OrElse.apply(PartialFunction.scala:162) ~[scala-library-2.10.4.jar:na] at com.redis.Reply$class.receive(RedisProtocol.scala:113)...
Maybe i am wrong, but i don't understand where "2" come from ?
I've started trying to use the "info" command programmatically to dynamically discover the master in a replication set. Unfortunately, the current implementation of the info command is expecting the wrong...
