V2: Not updating the Makefile generated config file produce a critical error

[lucassardois]

After doing the make init command a default conf.toml file is generated. If I try to run directly the benchmark using:

python control.py run-benchmark --config conf.toml -r runtime

I get the following error:

14:18:19| INFO     - Running benchmark: 99685ee4-6993-47f8-b827-cb66f6d4aa44
14:18:19| DEBUG    - Loading configuration from conf.toml
14:18:19| DEBUG    - Shells are running with -d
14:18:19| DEBUG    - Main benchamark loop
14:18:19| INFO     - Current dataset is tinkerpop-modern_mod.json
14:18:19| INFO     - Overriding java options: -XX:+UseG1GC -XX:MaxDirectMemorySize=512m
14:18:19| INFO     - Current database is orientdb
14:18:19| CRITICAL - Config not compatible with sample file. Suggested "sampling" conf:
14:18:19| CRITICAL - {"nodes": 3, "node_labels": 2, "node_props": 3, "edges": 3, "edge_labels": 2, "edge_props": 0, "paths": 0}     

I then have to edit the config file to set the paths property to 0. This happen to all DBMS. Should the tinkerpop-modern and air-routes datasets really have a sample paths of 0? Else, how to solve this?

[MartinBrugnara]

Please do not used tinkerpop* dataset for testing.

Air-routes, should work and have paths > 0.

[lucassardois]

Yep I updated it and it now works, thanks.