This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-07
Channels
- # aleph (10)
- # announcements (6)
- # architecture (23)
- # atom-editor (2)
- # beginners (35)
- # biff (5)
- # cljdoc (22)
- # clojure (14)
- # clojure-europe (18)
- # clojure-hungary (26)
- # clojure-nl (6)
- # clojure-uk (6)
- # clojurescript (39)
- # core-async (1)
- # data-science (14)
- # datascript (20)
- # datomic (4)
- # graalvm (18)
- # jobs-discuss (5)
- # keechma (1)
- # leiningen (4)
- # malli (3)
- # nbb (11)
- # nextjournal (2)
- # off-topic (1)
- # parinfer (1)
- # releases (1)
- # remote-jobs (3)
- # shadow-cljs (7)
- # sql (2)
- # xtdb (4)
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..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