[12.x] PredisClusterConnection::keys() #57841
Merged
+17
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split from #57714
Unskipping some more tests in RedisStoreTest. The're failing with
Cannot use 'KEYS' with redis-cluster.(see https://github.com/laravel/framework/actions/runs/19545929346/job/55964541433?pr=57841).Other commands like MGET, MSET, DEL fails only when keys hashes to different slots. Unlike them KEYS command is not working with cluster at all. See vendor/predis/predis/src/Cluster/ClusterStrategy.php, it does not lists KEYS command at all, meaning it will never found slot and node and allways fail.
As far as keys command was never really working with PredisClusterConnection, adding such method will not break any backward compatibility. keys method work same way as flushdb method, aggregating results over all nodes.
Couple not related to PR checks are failing