For the propagation of information, the system should possess a filtering capability.
On one hand, due to the update of Valkey, some commands are not in the old version, like EXPIREAT for 5.0, and thus if the version is not compatible, hybrid scheduling cannot be achieved.
On the other hand, this can enable the system to possess certain statistical capabilities.
At the same time, it is also closed-loop with the CommandFilter ability, and can do some control when synchronizing information externally
Description of the feature
Support an API in propagateNow, such as modulePropagateFilter, for processing argv. The following methods are supported:
modulePropagateFilters
RegisterPropagateFilter
UnregisterPropagateFilter
PropagateFilterArgsCount
PropagateFilterArgGet
PropagateFilterArgInsert
PropagateFilterArgReplace
PropagateFilterArgDelete
Alternatives you've considered
Use external components to synchronize, such as DTS.
Interesting, but I want to understand the full picture. Do you want to attach a 5.0 replica to a new Valkey? There is another problem: It can't do full sync because it doesn't know the new RDB version.
The problem/use-case that the feature addresses
For the propagation of information, the system should possess a filtering capability.
On one hand, due to the update of Valkey, some commands are not in the old version, like
EXPIREAT
for 5.0, and thus if the version is not compatible, hybrid scheduling cannot be achieved.On the other hand, this can enable the system to possess certain statistical capabilities.
At the same time, it is also closed-loop with the CommandFilter ability, and can do some control when synchronizing information externally
Description of the feature
Support an API in propagateNow, such as modulePropagateFilter, for processing argv. The following methods are supported:
Alternatives you've considered
Additional information
NA