This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-19
Channels
- # beginners (37)
- # boot (96)
- # cider (23)
- # clara (2)
- # cljs-dev (40)
- # clojars (1)
- # clojure (149)
- # clojure-conj (1)
- # clojure-dev (2)
- # clojure-dusseldorf (5)
- # clojure-france (82)
- # clojure-italy (1)
- # clojure-nlp (1)
- # clojure-russia (13)
- # clojure-spec (24)
- # clojure-uk (62)
- # clojurescript (131)
- # core-async (13)
- # core-logic (7)
- # data-science (1)
- # datomic (10)
- # defnpodcast (3)
- # docker (4)
- # emacs (3)
- # events (4)
- # hoplon (68)
- # klipse (4)
- # leiningen (1)
- # off-topic (5)
- # om (140)
- # onyx (16)
- # pedestal (24)
- # planck (10)
- # proton (2)
- # re-frame (9)
- # reagent (4)
- # remote-jobs (1)
- # ring-swagger (16)
- # untangled (5)
- # vim (8)
- # yada (30)
@whitecoop are you using the same version of Datomic on both peer and the transactor?
Also, you need to set the host property in the transactor properties file to an IP both the peer and transactor can resolve as the transactor machine
That was it. Fixed once I changed the host
property from localhost
to the actual IP. Thanks
The transactor.properties file for my ddb storage contains two AWS role properties: aws-transactor-role
and aws-peer-role
. Are these properties actually used at runtime by the Transactor? I suspect not, since I don't see any AssumeRole priv granted, so I'm guessing these properties are only for the ensure-transactor
. Is that correct?
I’m not certain, but that sounds right. datomic by itself doesn’t use or care about AWS roles, the roles should only be used for cloudformation stuff
Datalog question: are namespaced symbols officially supported for rule names ?