| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
also ensure unicode values are properly encoded
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Modifying comments for code documentation.
|
|
|
|
| |
Refactoring per our conversation on git.
|
|
|
| |
pep8
|
| |
|
|
|
|
|
| |
add_passwords is a string or list of passwords to add to the user
remove_passwords is a string or list of passwords to remove from the user
|
| |
|
|
|
|
|
|
| |
* The "enabled" flag now defaults to False
* Categories must be prefixed with "+@" or "-@"
* Commands must be prefixed with "+" or "-"
|
| |
|
|
|
|
| |
No tests yet for these as they depend on server configuration
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Redis and Connection classes now accept a username argument.
* URLs now look for and parse usernames.
* If a username is set, it is sent to the AUTH command when a connection
is established.
* NoPermissionError is raised in the event of a NOPERM response
|
|
|
|
| |
* Fix TypeError by passing optional decode_responses keyword argument down to parse_slowlog_get()
|
|
|
| |
Add equality test on Redis client and connection pool
|
|
|
| |
Sorry, I'm a pendant.
|
|
|
|
| |
keys
|
|
|
|
|
|
|
|
|
|
| |
The client section of MONITOR output varies for TCP connections, unix socket
connections and commands executed from Lua scripts. Account for each of these
cases by including an additional key `client_type` in the MONITOR output.
`client_type` will be one of ('tcp', 'unix', 'lua'). `client_address` and
`client_port` vary based on the `client_type`.
Fixes #1201
|
| |
|
|
|
|
| |
The PubSubWorkerThread now uses a `threading.Event` to control its life cycle.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `Redis` class and the `ConnectionPool` class now support the
"health_check_interval=N" option. By default N=0, which turns off health
checks. `N` should be an integer, and when greater than 0, ensures that
a health check is performed just before command execution anytime the
underlying connection has been idle for more than N seconds. A health
check is a full PING/PONG round trip to the Redis server.
If a health check encounters a ConnectionError or TimeoutError, the connection
is disconnected and reconnected and the health check is retried exactly once.
Any error during the retry is raised to the caller. Health check retries
are not governed by any other options such as `retry_on_timeout`. In systems
where idle times are common, these health checks are the intended way to
reconnect to the Redis server without harming any user data.
When this option is enabled for PubSub connections, calling `get_message()` or
`listen()` will send a health check anytime a message has not been read on
the PubSub connection for `health_check_interval` seconds. Users should
call `get_message()` or `listen()` at least every `health_check_interval`
seconds in order to keep the connection open.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has multiple uses:
* Single connection clients will not be considered threadsafe. This means
certain settings could temporarily be adjusted. For example, a context
manager could temporarily modify the encoding behavior for a set
of commands.
* We can introduce more thorough health checks that only happen when a
connection is handed out from the connection pool.
* Workloads that issue many commands to Redis should be slightly faster.
Prior to this change, the client must retrieve a connection from the
pool for each command.
|
|
|
|
| |
Fixes #1191
|
| |
|
|
|
|
|
|
|
| |
this change allows users to call client.execute_command('info') or
client.execute_command('INFO') and get the same parsed result.
Fixes #1168
|
|
|
|
|
|
|
| |
The Token class was needed when supporting Python 2.6. Now that we've
dropped support for 2.6, we don't need it anymore.
Fixes #1066
|
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Fix for https://github.com/andymccurdy/redis-py/issues/1135
|
| | |
| | |
| | | |
Fix for https://github.com/andymccurdy/redis-py/issues/1135
|
|\ \ \
| |/ /
|/| | |
|
| |/ |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Resolves a race condition found in the PubSubWorkerThread. Prior to this
change is was possible to receive the server's resonse to an unsubscribe
message prior to the channel/pattern being added to the
pending_unsubscribe set.
This also improves PubSubWorkerThread.stop so that the run function is
stopped immediately after the next iteration.
fixes #1150
|
|\
| |
| | |
1022: Fix retry logic for StricRedis and PubSub
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
GEOHASH response may contain None elements
|
| | | |
|
|\ \ \
| |/ / |
|
| | | |
|