@marshall @jaret Just thought you guys should know, I tried switching to the new CloudFormation console view when Amazon prompted, and when I tried to upgrade to 454 via https://s3.amazonaws.com/datomic-cloud-1/cft/454-8573/datomic-storage-454-8573.json (it's my first upgrade), I couldn't find the Reuse Existing Storage option. Once I switched back to the old console UI, it was there again.

i have a single ion function that routes my API, and quite often i get back a response: java.io.IOException: Connection reset by peer. a second or third try sometimes solves the problem. not knowing much about CloudWatch logs, how can i debug this?

Can I receive the last time an attribute was updated in datomic? Something like this, but this doesn't work:

(d/q '[:find (max ?tx-time)
                :in $ ?user
                :where
                [?user]
                [?user :user/password ?password]
                [?password _ _ ?tx _]
                [?tx :db/txInstant ?tx-time]]
              (d/db conn) 123))

Does anyone know what configuration is required (or recommended) when creating a Datomic Client instance while running on an Ion in the cloud?

- https://docs.datomic.com/cloud/ions/ions-reference.html#server-type-ion looks relevant for creating a local client to connect to a cloud system - https://docs.datomic.com/client-api/datomic.client.api.html#var-client covers the cloud and peer cases

I'm suddenly failing to start my development environment, it seems the Datomic-Cloud private Maven repo is refusing access:

My deps.edn is:

{:paths ["src"
         "resources"]
 :deps {org.clojure/clojure {:mvn/version "1.9.0"}
        com.datomic/ion {:mvn/version "0.9.28"}
        }
 :mvn/repos {"datomic-cloud" {:url ""}}
 :aliases
 {:dev
  {:extra-paths ["dev" "dev-resources"]
   :extra-deps {com.datomic/ion-dev {:mvn/version "0.9.186"}
                com.datomic/client-cloud {:mvn/version "0.8.71"}
                }}}}

Strangely this happens only when I start my REPL from an EC2 instance - it's fine on my laptop.

What region?

How do people usually evaluate the performance differences of Datomic queries? (without being impacted by the caching)

I'm getting "Assert failed: cfg" when trying to create a client instance in the Ion Cloud. I'm passing the config map:

{:server-type :ion
:system "my-system-name"
:region "us-west-2"
:endpoint ""}

@robert.mather.rmm https://docs.datomic.com/cloud/troubleshooting.html#assert-failed

@lwhorton I missed your reply a while back - the client API source is in the jar file

Hi, i’m having a weird problem (on 441-8505). Trying to transact a bigint of any form 1N (bigint 1) (biginteger 1) causes a “ExceptionInfo Cannot write 1 as tag null” error

is :db/index not a valid schema attribute in datomic cloud?

If I try to transact this:

(d/transact conn {:tx-data [{:db/ident       :foo/bar
                                 :db/valueType   :db.type/string
                                 :db/cardinality :db.cardinality/one
                                 :db/index       true}]})

Correct, everything is index true

@markbastian ^

everything is indexed in the cloud?

I can't wait to try this out.

Everything is indexed in on prem as well

is that true for in-mem?

That flag tells datomic to include that arrtibute in the AVET index

But all datoms are in eavt

And aevt

right, so can I put the attribute in avet?

Avet is "on" always in cloud

ok, so for on-prem avet is configurable, but cloud is always on?

Yup

ok, that makes sense

super cool

also, :db/unique also implies :db/index in on-prem

yep, got the unique part