This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-01
Channels
- # aws (2)
- # aws-lambda (18)
- # beginners (68)
- # boot (6)
- # cider (2)
- # clara (2)
- # clojars (27)
- # clojure (68)
- # clojure-austin (5)
- # clojure-berlin (6)
- # clojure-dev (28)
- # clojure-greece (7)
- # clojure-italy (46)
- # clojure-japan (3)
- # clojure-nl (1)
- # clojure-russia (8)
- # clojure-sg (1)
- # clojure-spec (17)
- # clojure-uk (86)
- # clojurescript (82)
- # community-development (2)
- # cursive (18)
- # datomic (11)
- # duct (5)
- # fulcro (254)
- # garden (2)
- # graphql (6)
- # hoplon (19)
- # instaparse (4)
- # kekkonen (2)
- # leiningen (4)
- # luminus (3)
- # lumo (9)
- # off-topic (28)
- # om (7)
- # onyx (38)
- # other-languages (27)
- # portkey (7)
- # protorepl (1)
- # re-frame (56)
- # reagent (64)
- # ring (14)
- # ring-swagger (7)
- # shadow-cljs (255)
- # sql (2)
- # vim (11)
- # yada (10)
I know Cloud’s storage impl permits low cost clones someday. What is it about Pro’s storage impl that prevents this? (`:restore/collision The database already exists under the name 'hyperblog'`)
@souenzzo Restore will put segments in DDB as fast as it can. You can increase your dynamo throughput or you can restart the restore process and allow it to finish. it will skip the segments it’s already copied
Not sure if S3 is slower, but restore from S3 works, restore from disk fail. My "default" workflow uses S3...
@souenzzo If you’re running the restore from a local process, I’m not surprised the S3 one is slower - it has to fetch segments from S3 then put them in DDB as opposed to put them directly from local disk into DDB
d/datoms, filtered to a specific partition - Anyone know the best way to do this?
Or even a way to discover what the starting entity number is for a given partition?
thank you