This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-04
Channels
- # beginners (46)
- # boot (65)
- # cider (8)
- # cljs-dev (5)
- # cljsrn (4)
- # clojure (50)
- # clojure-conj (2)
- # clojure-france (1)
- # clojure-greece (18)
- # clojure-russia (8)
- # clojure-spec (39)
- # clojure-uk (36)
- # clojurescript (36)
- # clr (16)
- # component (2)
- # cursive (6)
- # datascript (3)
- # datomic (31)
- # devcards (2)
- # editors-rus (1)
- # emacs (15)
- # events (2)
- # figwheel (1)
- # funcool (24)
- # garden (3)
- # hoplon (22)
- # instaparse (15)
- # leiningen (3)
- # luminus (4)
- # om (59)
- # onyx (24)
- # overtone (1)
- # pedestal (3)
- # planck (18)
- # prelude (1)
- # protorepl (2)
- # re-frame (5)
- # rum (1)
- # sql (1)
- # uncomplicate (1)
- # untangled (66)
- # vim (18)
- # yada (4)
Is this the best way of doing sorting/pagination in Datomic?: https://groups.google.com/forum/?nomobile=true#!msg/datomic/NgVviV9Sw8g/nXm3Lvkk2dwJ
If I see a huge spike in DynamoDB WriteCapacity units used (20,000 instead of the usual 200), could that be the transactor re-indexing/re-partitioning/doing some other kind of maintenance work?
@teng, I think it depends on your requirements
if you return modest number of results (<10,000 ?) I'd do this:
- d/q [:find ?e] (only query the entity id) - sort - subvec using the offset/limit provided - then do further transformations (another query, or d/pull or map d/entity(
if you want to use d/q, to my knowledge that's the best you can do as it always returns results unsorted
(looking at my list, you probably also need to include some sort of sort key in the query)
Ok thanks @pesterhazy - looks very similar to what Francis Avila wrote.
@pesterhazy Spikes in DDB write usage are definitely present during indexing jobs. You can look at memory index metrics and/or the logs to get an idea if there is an indexing job running
@marshall if usage exceeds provisioned capacity, does datomic work gracefully in that case?
you will get backoff and exponential retry for a period of time. too much throttling will result in transactor termination
makes sense
we haven't seen transactor failures due to indexing spikes yet, so the retry mechanism seems to be working
@marshall thanks!
Hi, I'm trying to back up a datomic db and am running into an obscure error that ends with java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter... not sure where to go from here. Anyone have any suggestions? https://gist.github.com/jdkealy/948068e40a47861c5d84b097bcbf39d5
@jdkealy can you post the backup command you’re running (elide any sensitive info like s3 paths or db names if necessary)
bin/datomic -Xmx4g -Xms4g backup-db datomic:<ddb://us-east-1/my-datomic-new/test-table> <s3://datomic-backups/backup1>
My suspicion is a classpath issue. Can you try downloading and unzipping a fresh distribution somewhere else on the box and running from there?
Is it possible to get the last transaction id for an entity when using the pull syntax?