Clarify that the migrate command populates the cache with data It wasn't obvious from the documentation that the REST-API /plugins/cache-chroniclemap/migrate was generating the new configuration and also copying the associated data from H2. Add a paragraph making the statement explicit and highlighting in details what the command does. Change-Id: I1073cd040d1512a4ba3f935afcc2e60a2d5f8a9c
Non-blocking and super-fast on-disk cache libModule for Gerrit Code Review based on ChronicleMap on-disk implementation.
This libModule is built like a Gerrit in-tree plugin, using Bazelisk. See the build instructions for more details.
Install the chronicle-map module into the $GERRIT_SITE/lib directory.
Add the cache-chroniclemap module to $GERRIT_SITE/etc/gerrit.config as follows:
[gerrit] installModule = com.googlesource.gerrit.modules.cache.chroniclemap.ChronicleMapCacheModule
For further information and supported options, refer to config documentation.
You can check how to migrate from H2 to chronicle-map here.