gitspeaks

Thanks. This method is effectively an “offline backup”. Please consider enhancing the engine to support backing up the database while the engine is running to a file that can be...

> We anticipate that HSE will most often be used as part of an application that has its own backup method. As far as HSE, what would be the correct...

Do you include KVDB/KVS snapshot version in each individual KVDB/KVS/KV object ?

Thanks. I’ll run some tests. Is this export api designed to run concurrently along other reader / writer threads or does it lockout writer threads while it writes out the...

@davidboles Thanks for clarifying! >One possible enhancement would be to allow it to be called on a KVDB with open KVS's and take an ephemeral snapshot at the beginning of...

@smoyergh Thanks, regarding my last query about relaxing hse_kvdb_export_exp() to work with a pre opened KVS, I should have added that this may allow an additional backup option if the...

> A method to dump a consistent snapshot of a live (online) KVDB is to create a transaction, which creates an ephemeral snapshot of all KVS in the KVDB, and...

About reclaiming the garbage, I assume this would be done during compact (e.g hse_kvdb_compact api). Is this the only way available to force GC “now” ? Does it block access...

Aside from having things neat for benchmarking I'm not clear on when one would use this api. hse.h, hse_kvdb_compact description: >In managing the data within an HSE KVDB, there are...

I think it would be beneficial if you expose some performance counters for this process including what you consider as “performance thresholds” to allow users to observe the engine dynamics...