auto_compaction controls background compaction while the HTTP service is running. It is serve-time behavior, not database-open configuration, so it should live on the serve path (ServiceConfig / Database.serve()), not on NeugDBConfig.
- Compaction is only started by
NeugDBService (e.g. via run_and_wait_for_exit()).
- Keeping it on
NeugDBConfig / NeugDB::Open(...) mixes open-time and serve-time options.
- Serve callers (Python
serve(), C++ ServiceConfig, rt_server) need an explicit knob for this behavior.
auto_compactioncontrols background compaction while the HTTP service is running. It is serve-time behavior, not database-open configuration, so it should live on the serve path (ServiceConfig/Database.serve()), not onNeugDBConfig.NeugDBService(e.g. viarun_and_wait_for_exit()).NeugDBConfig/NeugDB::Open(...)mixes open-time and serve-time options.serve(), C++ServiceConfig,rt_server) need an explicit knob for this behavior.