Pipelining doesn't supports time operation [DATAREDIS-513]

[spring-projects-issues]

Yanming Zhou opened DATAREDIS-513 and commented

List<Object> results = (List<Object>) stringRedisTemplate.executePipelined(new RedisCallback<Object>() {
     @Override
     public List<Object> doInRedis(RedisConnection connection) throws DataAccessException {
          connection.incr("test".getBytes());
          connection.time();
          return null;
     }
});
System.out.println(results);

redis.clients.jedis.exceptions.JedisDataException: Cannot use Jedis when in Pipeline. Please use Pipeline or reset jedis state .
	at redis.clients.jedis.BinaryJedis.checkIsInMultiOrPipeline(BinaryJedis.java:1671)
	at redis.clients.jedis.BinaryJedis.time(BinaryJedis.java:3226)
	at org.springframework.data.redis.connection.jedis.JedisConnection.time(JedisConnection.java:3184)
	at org.springframework.data.redis.connection.DefaultStringRedisConnection.time(DefaultStringRedisConnection.java:2365)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.data.redis.core.CloseSuppressingInvocationHandler.invoke(CloseSuppressingInvocationHandler.java:57)
	at com.sun.proxy.$Proxy142.time(Unknown Source)

---

Affects: 1.7.1 (Hopper SR1)

Referenced from: pull request #199

Backported to: 1.7.2 (Hopper SR2), 1.6.5 (Gosling SR5)