Fork me on GitHub

Are there any guides or tips for migrating from datomic-free to pro (on-prem)?


How would one create a library for datomic ions? What would be the contents of the library’s deps.edn file? Would it be best to consider the ion and client cloud libs as “provided”?

Alex Miller (Clojure team)13:10:26

you might want to check out the ion-starter project


Thanks, Alex. I’ve studied that example extensively, and my impression was that it was more application focused. I’m thinking of adding an alias to my library’s deps.edn file called :provided that contains all of the relevant datomic libs. Then users of the lib would need to depend on those themselves.

Alex Miller (Clojure team)14:10:25

that seems like a reasonable approach

Alex Miller (Clojure team)14:10:59

or you could just depend on them directly - the users of your lib could specify different versions and those would be preferred


Ah okay, that was where my confusion was. I’m never quite sure when, as a lib author, a dependency should be considered “provided” @alexmiller. Probably a question for #tools-deps, but it sounds like the resolution is “last one wins”?


(shared to #tools-deps to stay on topic, FYI)


Hi, I'm currently writing a custom monitoring solution in order to enable Prometheus scraping transactor metrics. The monitoring documentation ( doesn't seem to completely represent the current state of metrics handed to a callback function by the transactor. For specific metrics, information is hidden in the changelog section and never made its way to the monitoring documentation. Other metrics are said to be deprecated (since a long time ago) in favor of replacements, although these replacements were never handed over by the transactor. So 2 questions: - is there a plan to update the documentation on this topic in the near future? - what do the metrics PodUpdateMsec and PodGetMsec describe?


Is it possible to pull the transaction data for a datom without binding a ?tx in the :where clause? For an example close to the specific problem I'm trying to solve: - could the final pull be modified to include (say) db/txInstant with each item of :release/_artists?


Research question: is there a way to hook up Datomic Cloud Analytics to an AWS instance of Metabase? I realize I would have to run an EC2 instance, etc. and I am willing to put in the work, but I need to know it's possible...


We did this just today: Easiest is to run the analytics ssh tunnel from the EC2 instance, and then let Metabase connect to local host. Also, it's so darn sweet to see the data in Metabase.

👍 4

I'm trying to convince a client to start paying for Datomic - where can I find guides or tips for migrating from datomic-free to pro (on-prem)?


I’m not sure there’s any migration to do? backup the db, restore it to your new storage. If you’re still using dev storage, you may not even need backup+restore (I’m unsure)


are you aware of the distinction between “starter edition” and “free”?


starter edition is just a free-first-year license-key


Yes, part of the selling point is that they don't have to pay the first year. I tried pointing datomic-starter at the same URL, but there's no free there, and dev does not see the contents from the free database. A backup+restore sounds entirely doable, but I'd be interested in cleaning up the database a bit at the same time. I think it's called decanting?


Does the connection work if you s/:free:/:dev:/?


They’re the same bytes in storage really, only some runtime license/feature checks are different


Oh you did try it. Huh I expected that to work


is squuid only in datomic peer or can i generate a squuid in the datomic cloud api?


Where's the best to report issues with Datomic documentation? I've run into a couple dead links and outdated instructions recently (though I'll have to find them again to be able to report them).

Alex Miller (Clojure team)20:10:56

here is usually a good place


I'm getting tons of these: clojure.lang.ExceptionInfo: :db.error/transactor-unavailable Transactor not available and I'm not sure how to diagnose. The transactor is up and running and it doens't look like it's that bogged down. Is there an easy way to diagnose this error or to get more information?


Most of my "transactor unavailable" errors with on-prem were due to a lack of heap on the peers. Hope that helps.


resource starvation on the peers would be my first check too. you could wrap d/transact with some monitoring to measure average completion time.


@alexmiller Perfect, thanks! I think these were the only one I ran into, but I'll post here if I find any others. Broken Link - (found in and Outdated instructions - the AWS pages used when following and have changed - they've removed the "Actions" button and have a standalone "Update" button, and the options for specifying the S3 Template are named differently as well. Not sure if that's universal or if it depends on the account or region.

Alex Miller (Clojure team)21:10:41

thx, I'll ship 'em to datomic team