Open GoogleCodeExporter opened 8 years ago
The main problem I have with doing this is that it changes the exported
semantic at run-time. All the configuration directives have effect on the inner
workings of Redis, while the behavior doesn't change. In addition, Redis is
currently unable to persist its configuration to disk. When there are commands
that are renamed at run-time, the exported set of commands changes across
restarts. Instead, when the rename statements are issued via the configuration
file, this is made explicit and is less likely to result in errors (expecting a
command to be renamed after restart while it isn't).
This all follows from the fact that the configuration cannot be persisted at
the moment which would be a great feature to begin with (although it has its
own set of problems).
Leaving this open for now because it is interesting and I don't want to rule it
out just yet.
Original comment by pcnoordh...@gmail.com
on 22 Aug 2011 at 1:42
+1 for resolving this because of the following use case: in hosted Redis
environments the config files are usually not accessible to users so the
simplest way is to allow CONFIG for supported operations. Maybe the way to
resolve the main problem is to disconnect all clients after changing exported
semantics at runtime.
-1 for "in addition": 2.8 added config-rewrite
Original comment by ita...@garantiadata.com
on 4 Feb 2014 at 5:11
This google project is outdated. Please report the issue on
https://github.com/antirez/redis
Original comment by jeredi...@gmail.com
on 4 Feb 2014 at 5:30
Original issue reported on code.google.com by
naranj...@gmail.com
on 19 Aug 2011 at 7:42