This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-29
Channels
- # architecture (14)
- # beginners (184)
- # boot (25)
- # cider (23)
- # clara (9)
- # cljsjs (13)
- # cljsrn (5)
- # clojure (140)
- # clojure-austria (1)
- # clojure-dev (24)
- # clojure-greece (15)
- # clojure-italy (7)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-sanfrancisco (10)
- # clojure-spec (39)
- # clojure-uk (28)
- # clojured (1)
- # clojurescript (26)
- # core-async (3)
- # cursive (13)
- # datomic (44)
- # docs (3)
- # emacs (31)
- # events (2)
- # figwheel (4)
- # fulcro (6)
- # graphql (2)
- # hoplon (5)
- # jobs (11)
- # juxt (4)
- # keechma (19)
- # leiningen (1)
- # off-topic (8)
- # om (8)
- # onyx (18)
- # parinfer (2)
- # re-frame (18)
- # reagent (24)
- # ring (4)
- # rum (2)
- # shadow-cljs (26)
- # sql (15)
- # timbre (6)
- # vim (2)
Hello folks, I'm trying out datomic cloud
I have set it up and I can connect to the instance on aws through the bastion using the ssh proxy
Now I'm deploying a simple lambda function to test the connection and I get an unavailable error
"errorMessage": "Unable to connect to system: {:cognitect.anomalies/category :cognitect.anomalies/unavailable, :cognitect.anomalies/message \"Connect Timeout\" ..}
I'm using the same config I use for the basion connection, removing the proxy-port map
{:server-type :cloud
:region "eu-west-1"
:system "datomic-cloud-demo"
:query-group "datomic-cloud-demo"
:endpoint " "}
And I have the lambda running on the same VPC as datomic
@marshall FYI client-api docs linked to from cloud (https://docs.datomic.com/cloud/client/client-api.html) point to on-prem docs in the q
docstring (https://docs.datomic.com/client-api/datomic.client.api.html#var-q), since there are two client libraries now (cloud and on-prem), it should probably point to both or have separate docs?
@frankie you’d have to authorize security group ingress from the security group you’re running the lambda in
Excellent, thanks!
Ok, now I've got a different error
"errorMessage": "Unable to execute HTTP request: Connect to [] failed: connect timed out",
Mhmhm, I've added that but it didn't change the error
I will have a closer look, but thanks for the help so far!
@stuarthalloway are :db.type/keyword
less storage efficient than :db.type/ref
-as-enum? other than the cool VAET trick where you can d/entity
-reverse-walk to references of an enum value, why would I use enums over keywords? so far, i’m finding that the api for keywords is far nicer — no having to handle idents in d/pull
or d/q
when using keywords, for instance.
it does seem to be faster to use enums over keywords in Datalog, likely because of the under-the-hood switch to entity ids there
@robert-stuttaford I would not worry about perf — use enums only if you need them for something keywords can’t do
right - such as adding other AVs alongside the ident
thank you
@robert-stuttaford going back to an earlier question: squuids are ancient, not particularly important since http://blog.datomic.com/2014/03/datomic-adaptive-indexing.html
wow. shows how ancient my knowledge is 🙂 i’ve been religious about using squuid
on our team. one less thing to worry about…
@robert-stuttaford @denik updating the docs about other On-Prem/Cloud questions, will update you here
thank you Stu - your quick response is appreciated!
https://docs.datomic.com/on-prem/clients-and-peers.html#peer-only < Updated differences between clients & peers
@marshall - is there a similar table or doc comparing on-prem client api to peer server and cloud/client?
thank you @marshall!
I am currently experimenting with the Client API using [com.datomic/client-pro "0.8.14"]
(rather than [com.datomic/client-cloud "0.8.50"]
). It seems as if the Client does neither implement (delete-database [_ arg-map])
nor (create-database [_ arg-map])
of the Client protocol. Is that by design or just for now?
That’s correct @jocrau - using client with Datomic on-prem you’ll need to do the delete or create database calls from a peer
@stuarthalloway what aspect of Adaptive Indexing obviates the need for squuids?
“Sustainable import rates independent of db size” could also include “… and independent of distribution of data values”
@souenzzo @val_waeselynck the explanation of as-of + with at https://docs.datomic.com/cloud/time/filters.html#as-of-not-branch covers all usage in Datomic, whether cloud or on-prem, client or peer. Does that answer the original question?
@stuarthalloway well, if you confirm that long-lived db values may get resolved via asOf
on the server-side, it follows that with()
is broken on clients