This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-28
Channels
- # announcements (5)
- # asami (34)
- # babashka (15)
- # beginners (222)
- # calva (5)
- # cider (2)
- # circleci (4)
- # cljfx (11)
- # clojure (34)
- # clojure-europe (10)
- # clojure-nl (2)
- # clojure-taiwan (2)
- # clojure-uk (5)
- # clojurescript (27)
- # conjure (8)
- # cryogen (11)
- # cursive (11)
- # datomic (7)
- # depstar (6)
- # fulcro (29)
- # graalvm (2)
- # joker (3)
- # kaocha (9)
- # nrepl (4)
- # off-topic (9)
- # pathom (1)
- # shadow-cljs (11)
- # spacemacs (4)
- # sql (1)
- # tools-deps (12)
I was trying to run datomic on AWS but when I want to create-database I get an error:
Execution error (Exceptions$IllegalArgumentExceptionInfo) at datomic.error/arg (error.clj:79).
:db.error/invalid-ddb-region Not a supported dynamodb region: me-south-1
Any idea how to fix this?
AWS supports dynamodb in me-south-1: https://docs.aws.amazon.com/general/latest/gr/ddb.html
which datomic is this? cloud or on-prem? Cloud is only supported on certain regions (this isn’t one of them, list here https://docs.datomic.com/cloud/operation/account-setup.html#regions). On-prem might just have an out of date sdk that doesn’t know about this region?
@U017D57461Z how are you creating the DB and what docs are you following? Can you share the command you are using for on-prem? Are you using client or peer api? For on-prem you need to roll your own CFT. Have you done so? As a development connivence we provide an example template through our create-cf-template script. https://docs.datomic.com/on-prem/aws.html However you also have to configure storage: https://docs.datomic.com/on-prem/storage.html#provisioning-dynamo
Hey! I'm trying out Datomic Analytics Support, I don't know where to put the metaschema .edn
-files. They do not seem to be picked up when placed in ./presto-server/etc/x.edn
on my datomic-peer installation, should they be somewhere else?
Configuration / catalog is all setup, and show tables
shows the default db__attrs
and db__idents
columns. My metaschema.edn is also correct, see thread.
Very simple metaschema:
{:tables
{:person/id {}}
And I verified that (d/q '[:find (count ?e) :where [?e :person/id]] db)
returns non-zerohttps://docs.datomic.com/on-prem/analytics/analytics-configuring.html#configuring-metaschema
describes etc-path/datomic
, where etc-path
is announced by presto as the Etc directory:
(no surprises there).
so in my case; opt/datomic-pro-1.0.6202/presto-server/etc/datomic/x.edn
worked. :thumbsup::skin-tone-2: