Releases for Redis

Drupal 10 compatibility, bugfixes

Contributors (4)

Berdir, Project Update Bot, aramboyajyan, maximpodorov

Changelog

Issues: 3 issues resolved.

Changes since 8.x-1.5:

Various bugfixes, Drupal 9 and PHP 8 compatibility fixes and support for persistent connections.

Contributors (16)

hugronaphor, mhavelant, cafuego, anish.a, eelkeblok, Dave Reid, jmullikin, carolpettirossi, Berdir, hussainweb, sharma.amitt16, bceyssens, shaktik, mvantuch, jonhattan, harishh

Changelog

Issues: 8 issues resolved.

Changes since 8.x-1.4:

Race condition fixes, statistics page and support for gz compression

Contributors (9)

jcisio, Berdir, O'Briat, vomiand, driki_, eiriksm, slasher13, davidwhthomas, nitesh624

This release requires Drupal 8.8

This release contains 3 major improvements:

Compatibility with php-redis 5 and other bugfixes

Contributors (13)

Dave Reid, anish.a, jmullikin, zerolab, alesr, jurgenhaas, melsi, Berdir, michele.lucchina, shobhit_juyal, Pranjal.addweb, Krasnyj, hey_germano

Changelog

Issues: 8 issues resolved.

Changes since 8.x-1.1:

PHP 7.2 compatibility and other bugfixes

Contributors (3)

Erik Frèrejean, Berdir, neclimdul

Changelog

Issues: 2 issues resolved.

Changes since 8.x-1.0-rc2:

This fixes a critical regression in the 8.x-1.0-rc1 release which caused a fatal error.

Changes since 8.x-1.0-rc1:

• #2908741 by dtv_rb: Syntax Error in ClientFactory.php

This release includes an improved default cache prefix that works consistently for multiple domains and drush commands as well as support for improved serialzation using the igbinary module.

This is a maintenance release that fixes minor documentation details and case sensitivity for path alias handling.

Full changelog:

• #2793635 by ckohl: Normalize database return for static caching
• #2793635 by czigor, ckohl, pounard: Case sensitive URL caching
• #2788585 by kunal.kursija: README.md grammar error
• #2752735 by fgm: Doc mentions removed session component

First alpha release of redis for Drupal 8.

Note:

The current version does not yet support sharding, see https://github.com/md-systems/redis/pull/7

This is a minor maintainance release, a few annoyances are fixed.

• Issue #2666866 by DamienMcKenna: Unable to run tests: Class 'Redis_Tests_Cache_FixesUnitTestCase' not found
• Issue #2556643 by joelpittet, RobLoach, meelis82: PHP 5.3 compatibility
• Issue #2648148 by thewilkybarkid: Exception on Drupal status page
• Issue #2684303 by attiks, NWOM: md5() expects parameter 1 to be string, array given in Redis_Client::getGlobalPrefix()

Maintenance release that comes with a few fixes. As always it is strongly recommended that you upgrade.

This release should fix a Predis autoloader blocking issue, and bring performance improvements in utility methods that will be a significant benefit for all users.

Changelog:

• Issue #1839434 by garnett2125, pbuyle, floretan, pounard, DuaelFr, weri, pivica: Class 'Predis\Client' not found
• Pending issue #2550275: redis_autoload() optimization
• Pending issue #2550275: Redis_AbstractBackend::getKey() optimization

Fixes a single bug that may cause some users to experience PHP segfault due a php-redis bug under certain conditions.

• Issue #2522966 by das-peter: Possible segfault because of new volatile flag (probably only php_redis < 2.2.7)

Upgrading to this version is important for all Drupal 6 / Cache Backport module users only.

Full changelog:

• Issue #2189275: (Cache Backport compat) Fatal error while requiring database.inc and accessing \Database
• Issue #2402567 by GoZ: Add drush command to flush DB
• Fixed wrong type errors in lua scripts, some tests still failing

This new release brings the ability to configure the cache backend to use EVAL commands to greatly speed up cache clearing thus fixing the issue #2415705: Timeout when clearing large databases.

Per default, EVAL commands are disabled and can be enabled by adding to your settings.php file:

This is probably the most stable release ever, even more than the 2.x branch; nevertheless the 3.x is still going to evolve much yet, reason why it's still not recommended in production.

The cache backend has been almost fully rewritten, thanks to all testers and contributors, and unit tests proven to be useful and have been heavily extended to numerous edge cases and various non regression testing.

The cache backend should now be ready for sharded environment usage, using twemproxy or any other sharding proxy, although it's still lack testing at this time.

This new release brings numerous features and bugfixes, if you are using the 3.x branch you are urged to upgrade to this version.

The most awaited new feature is the ability to set a server pool in configuration (documentation to be written still) - This won't be used as of now by the cache, lock, path or queue implementation, but provides a public API for external users that would use multiple Redis servers for various business reasons. This feature remains experimental as the way it's to be configured is not stable and still unused yet by the provided backends.

This release only fixes one serious bug: getMultiple() function was sometime returning duplicated entries as arrays, causing the caller to fail reading it when not relying on the $cids arrays. This especially caused troubles with CTools.

This is the first almost stable - yet untested on production environment - of the 3.x version of this module.

Please test it carefully before upgrading on existing production environments. Any kind of feedback is welcome. Beware that the EVAL command as of today makes it non-shardable, solution(s) are still being investigated.

Major changes are mostly internal:

This is maintainance release which contains a few bugfixes and documentation improvements along with working UNIX socket connection, and a new experimental queue implementation.

Full changelog:

All users which are using 7.x-2.7 and 7.x-2.8 version should upgrade right away. I missed some typos in the last two releases and this may cause you some trouble if you are using more than one site in the same Redis instance and database.

Once again, if so and if you did upgrade, you'll need to FLUSHDB your Redis instance.

One noticeable feature change is that Predis path.inc replacement is now included. Path lookup has been manually tested (no units tests yet there sorry) and should be fully working now, still waiting for feedback of course.

Complete changelog:

This is both a bugfix and a feature release.

WARNING: path.inc replacement is experimental and does not flush correctly when aliases are updated: do not use this feature in production. New release will come soon.

The default automatic cache prefix has changed, be careful if you update, you may need to proceed to a Redis FLUSHDB command to avoid stalling entries.

If you are anot affected by a FLUSHDB then it is strongly recommended that you update to this release.

Changelog:

Added prefix support for lock backend.

Important update fixing the cache clear behavior among other problem. Previous version was stalling cached pages when the "cache_lifetime" was set to 0, causing serious cache stall issues on aggressively cached environements.

Everyone that updated to the 2.0 release MUST upgrade!.

Fixes a bug found by msonnabaum, regression from the bug #1980250: temporary cache items were invalidated right away when stored while the 'cache_lifetime' variable was set to 0 (recommended default) which caused permanent cache rebuild for every temporary item.

This release adds full unit testing of the lifetime handling in this module.