InfluxDB 2 upgrade needs two options for specifying target paths. Both options are the same as influxd run uses:
-e | --engine-path, path to the engine folder, default <user-home>/.influxdbv2/engine
-b | --bolt-path, path to the bolt DB file, default <user-home>/.influxdbv2/influxdb.bolt
The most confusing thing seems to be the bolt DB path. A user needs to add a full path to the specific file, which doesn't exist yet. The improvement would be specifying just a folder, e.g., --bolt-dir.
However, it would be more clear if there is is just a single option e.g. --v2-dir to specify ve folder, default <user-home>/.influxdbv2/. And implementation would just extend that into two necessary paths.
InfluxDB 2 upgrade needs two options for specifying target paths. Both options are the same as
influxd run
uses:-e | --engine-path
, path to the engine folder, default<user-home>/.influxdbv2/engine
-b | --bolt-path
, path to the bolt DB file, default<user-home>/.influxdbv2/influxdb.bolt
The most confusing thing seems to be the bolt DB path. A user needs to add a full path to the specific file, which doesn't exist yet. The improvement would be specifying just a folder, e.g.,
--bolt-dir
.However, it would be more clear if there is is just a single option e.g.
--v2-dir
to specify ve folder, default<user-home>/.influxdbv2/
. And implementation would just extend that into two necessary paths.