This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-19
Channels
I tried to use crux-http-server, with either rocks-db or jdbc, and in both, I seem to have a dependency issue, whereby I never find crux/rocksdb or crux/jdbc, while I added them both in my dependenicies.
Hi, I've not encountered an issue like that so far ๐ Can you share your module config map? Did you have something working correctly with a previous version?
I just tried the examples
using the command line, but let me try again.
Here are the config files? Do you think I am doing anything wrong?
Hi @UEQGQ6XH7 sorry for the delay. I think I'm reproducing the issue here also when running the CLI version via clojure -m crux.main
- is that what you were doing also? Normal repl usage seems to be fine for me in any case
Thanks for confirming. We'll be looking into and report back soon. In the meantime I trust the repl is working okay?
What was your crux/entity
issue? Was it not returning documents that were visible when using crux/q
? If so, that's usually a symptom of having persisted the index-store but not the doc-store when restarting the node
@UEQGQ6XH7 okay so there's no bug as such, but certainly some small clarity needed in the docs. Your crux.edn should work fine without any use of io/file
or '
:
{:crux.http-server/server {:port 3000}
:rocks-db {:crux/module crux.rocksdb/->kv-store
:db-dir "/tmp/rocksdb"}
:crux/index-store {:kv-store :rocks-db}
:crux/document-store {:kv-store :rocks-db}
:crux/tx-log {:kv-store :rocks-db}}
Arguably we could relax the requirements at some point but I'll see that the docs are updated in the first instance. Sorry about the confusion there ๐Thanks!
No, thank you for giving it a go and flagging up the problem ๐ Did you have any further thoughts on the entity issue (as per my last-but-one message)?
I donโt remember to having raise any issue with crux/entity :face_with_monocle:
Ah, my mistake, you used the word "entity endpoint" (https://clojurians.slack.com/archives/CG3AM2F7V/p1600548249007900) so presumably the http version of entity?
ah yes, let me check when I can use it again.
Anyone had a similar issue?
I also have some issue using the entity endpoint.