DATAREDIS-132, DATAREDIS-130, DATAREDIS-152
- Upgrade to fix broken config_get in SRP 0.2
- Fix syntax errors in sort methods
- Fix syntax errors in zRange/zRevRange methods
with offset and count
executed in the tx
DATAREDIS-123
- Close pipeline on exec if not explicitly
opened by user and return results of closePipeline,
not result of exec command
- Close pipeline on discard if not explicitly
opened by user
- Prevent simultaneous write of subscribe/unsubscribe using the same Connection
- Fix test failure by re-initializing "done" state of SubscriptionTask between runs and adding waits
DATAREDIS-124
- Close connection when SubscriptionTask is canceled and subscribing thread is unblocked
- Ensure non-blocking Lettuce and SRP only attempt
to close subscriptions if active
- Cleanup unecessary synchronization between
SubscriptionTask methods, now that connection is
no longer set to null
- Cleanup unused monitor notify when SubscriptionTask thread ends
- Add tests for all Connection methods
- Add tests for all Connection methods through pipeline
- Clean up DB between Connection test runs
- Reduce sleeps in pub/sub tests to improve execution time
- Use Spring integration test support to instantiate ConnectionFactory
once per instance of test class (instead of per method)
- Minimizes number of connection factories and thus connections
in pooled scenarios
While the (hash) increment() method accepts a long argument (and Redis
HINCRBY/INCRBY/DECRBY treats arguments as 64 bits), it is cast to a
32bits signed int in the JedisConnection class.
- Removed offensive (& unnecessary) casts
- Extended integration tests with incrBy, decrBy and hIncrBy to
demonstrate handling of large numbers
- Fixed typos in test support
(CollectionTestParams, AbstractConnectionIntegrationTests)
Issue: DATAREDIS-117
SRP unsubscribes asynchronously, so occasionally not all messages were delivered prior to unsubscribe. Test will now unsubscribe on connection close instead.
- DATAREDIS-118
- Change method return type back to void to fix backwards
compatibility issues
- Modify tests to assert specific clients receive or
don't receive messages vs comparing expected client counts
