This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-27
Channels
- # aws-lambda (3)
- # beginners (3)
- # boot (327)
- # capetown (2)
- # cider (156)
- # cljs-dev (368)
- # cljsjs (13)
- # cljsrn (53)
- # clojure (403)
- # clojure-czech (5)
- # clojure-dev (4)
- # clojure-greece (2)
- # clojure-russia (72)
- # clojure-spec (12)
- # clojure-uk (129)
- # clojurescript (156)
- # core-async (1)
- # cursive (33)
- # datomic (35)
- # emacs (10)
- # events (1)
- # hoplon (4)
- # jobs-discuss (3)
- # klipse (1)
- # lein-figwheel (14)
- # leiningen (5)
- # luminus (5)
- # off-topic (15)
- # om (69)
- # om-next (2)
- # onyx (2)
- # parinfer (15)
- # perun (12)
- # re-frame (30)
- # reagent (7)
- # ring-swagger (8)
- # spacemacs (10)
- # specter (6)
- # untangled (69)
- # yada (13)
@bballantine and
in Datomic datalog query isn't precisely the same thing as clojure.core/and
. As I read it, [?p1]
would bind ?p1
to the entity position in a datom.
@favila Thanks, now both works! It was hard to figure out when reading the documentation. Still waiting for that book that Stu is going to write 😉
Hi, regarding s3 log rotation, what does cognitect mean with time-status-reached
on:
* Better naming convention for logrotation:
`{bucket}/{system-root}/{status}/{time-status-reached}`,
where status is "active" or "standby".
Does anyone happen to know how to interpret the GarbageSegments
CloudWatch metric? I assumed it would be an accumulation of unreferenced segments over time, but it appears to go up and down.
And I don't see it on the http://docs.datomic.com/monitoring.html page
Anyone else seeing lein deps
failing on org/javassist/javassist/3.18.1-GA/javassist-3.18.1-GA.jar
?? I believe it’s a dependency of com.datomic/datomic-pro “0.9.5372"
Retrieving com/datomic/datomic-pro/0.9.5372/datomic-pro-0.9.5372.jar from
Could not transfer artifact org.javassist:javassist:jar:3.18.1-GA from/to central ( ): Checksum validation failed, expected d9a09f7732226af26bf99f19e2cffe0ae219db5b but is 1153878fa3db0c164318521e8e77106f9099f4e5
I’m fairly new to all this so feel free to redirect if this isn’t the appropriate channel. this is quite strange though, a routine build began to fail and now it’s affecting all developers
I'm getting this:
Could not transfer artifact org.javassist:javassist:jar:3.18.1-GA from/to central ( ): Checksum validation failed, expected d9a09f7732226af26bf99f19e2cffe0ae219db5b but is 1153878fa3db0c164318521e8e77106f9099f4e5
Adding this exclusion fixed the deps but possibly broke ring:
[ring-middleware-format "0.7.0"
:exclusions [org.clojure/test.check com.cognitect/transit-clj]]
Looks like @r0man has got our backs: https://github.com/jboss-javassist/javassist/issues/120
is it normal for a query like this to take up to 10 mins with datomic ? 2 organizations, 10k collections, 2.5 million "content" https://gist.github.com/jdkealy/b9d62366c46ba078051bad849e82c200
@jdkealy You can learn a bit about the behavior of a query by executing each :where
clause separately.
In your example, start with [:find ?collection :in $ ?org :where [?collection :collection/organization ?org]]
, then add the next clause, and so on.
You can also think about how indexes will be used to resolve each clause in the query. Since you start with a binding for ?org
, it's a single lookup in VAET
to get ?collection
, then another VAET lookup for ?content
, finally a separate EAVT
lookup for each ?content
to get ?fk
, then an iteration to find the max.
@jdkealy Most of those lookups will probably be handled from the Peer's local cache, after warmup. But if ?content
entities are large or randomly distributed there might be a lot of EAVT
segments to fetch to answer that query.
got it thanks @stuartsierra i realized i didn't have an index on content/collection... that appears to be making it extra slow
if i were to jack up memory locally... would i do so on the transactor or when starting my server
not on the transactor, on the peer