@casperc per: https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/BlockingQueue.html “ A BlockingQueue does not intrinsically support any kind of "close" or "shutdown" operation to indicate that no more items will be added. The needs and usage of such features tend to be implementation-dependent. For example, a common tactic is for producers to insert special end-of-stream or poison objects, that are interpreted accordingly when taken by consumers."

@marshall If you lose the reference to the queue will it be deallocated?

If I update some of the values on a component entity as part of a transaction on the parent entity, I’ve noticed that a new component entity is created, instead of it’s values being updated. Is there some way to update component attribute values as part of a transaction on the parent?

IE:

;; What I’m currently seeing:

(:person/address (d/pull db '[{:person/address [*]}] tony-soprano))
;; => {:db/id 1234 :address/city “Newark” :address/state “NJ”}

(d/transact
  conn
  [{:db/id (:db/id tony-soprano)
    :person/first-name “Tony”
    :person/address {:address/state “New Jersey”}}])
;; => #object

(:person/address (d/pull db '[{:person/address [*]}] tony-soprano))
;; => {:db/id 5678 :address/state “New Jersey”}

Discovered that adding in :db/id as part of the nested component prevents that from being automatically assigned a new one

Hi all... Is there an easy way to see whether a datomic transactor is the primary or failover transactor (in a set of 2)? I'm thinking about trying to run automated datomic backups from the failover one only

The log will report a standby metric

The active transactor writes its location into storage for peers to find it. The passive or standby transactors do not so you would have to look into the transactor logs for the metric

Why doesn't datomic.query.EntityMap implement Clojure's metadata interfaces?

Thanks @jaret, will see what I can do with that