Fork me on GitHub
#xtdb
<
2022-07-07
>
plins16:07:00

not necessarily a xtdb issue but maybe there is a way around configuring it: Im currently using duct, and it basically merges the prod config with the test one, merging the prod values with the test values the thing is, I want to run the tests in memory. passing an empty object cfg {} to xtdb does the job but when I merge an empty map with the ones containing production cfg I get the production cfg back, obviously is there a way to configure an in memory database using this cfg format?

{:xtdb/tx-log {:kv-store {...}}
 :xtdb/document-store {:kv-store {...}}
 :xtdb/index-store {:kv-store {...}}}
instead of passing an empty hashmap? in this way the test cfg would actually replace the production one..

refset17:07:51

Hey, absolutely! {:kv-store 'xtdb.mem-kv/->kv-store} x3

plins17:07:10

thank you ❤️

💫 1
refset17:07:48

I don't fully understand the plumbing of the module system (😅) but you can see an example of the underlying default config here: https://github.com/xtdb/xtdb/blob/5a74c9fe91c8ca26cdfb2832171a439ad25d5541/core/src/xtdb/kv/tx_log.clj#L120