Fork me on GitHub
#datomic
<
2019-06-21
>
Brian Abbott03:06:10

... if I am using Datomic Cloud, can I inspect/unsder stand its performance charataristics using AWS X-Ray?

Brian Abbott03:06:25

Has Datomic incorporated X-Ray into Cloud or Ions?

steveb8n06:06:23

@briancabbott if you use pedestal as your web server then you can use the open-tracing sample, although that doesn’t save to x-ray. I want to do the same thing. I’m planning to use the aws client to save spans in my Ion code

👍 4
Katie Lefevre17:06:01

Hi Folks. We have an old datomic/cassandra cluster and are seeing some weird behavior. We're using https://github.com/bostonaholic/datomic-export to export a csv. It's working for most tables but not for a few very small reference tables. This is probably not enough info, so please let me know what other details I should provide. Appreciate any and all help!

favila17:06:23

What is a "table"? what does "working" and "not-working" look like? (i.e. what is your get vs expect?)

Katie Lefevre17:06:20

Ah, yes. We definitely are new to datomic

Katie Lefevre17:06:50

A particular set of attributes

Katie Lefevre17:06:08

are empty? I suppose? when we see that they are populated if we check the entity id

favila17:06:26

are you seeing rows in the csv you don't expect to see, or with unexpected results, or...?

Katie Lefevre18:06:46

No we're seeing no rows

Katie Lefevre18:06:12

I think we have a way around it using the ui...

favila18:06:27

ui of what?

favila18:06:54

datomic-export is best used with a specific list of attributes to export

favila18:06:00

(the "include" argument)

favila18:06:26

you will then get only those entities with any of those attributes. if no entities have any assertions on those attributes, you will get no rows

favila18:06:18

if you don't supply an "include" argument, you're going to get every entity with any attribute, plus you're going to eat a lot of memory while it figures out what those entities are

Katie Lefevre18:06:23

thanks favila!

johnj23:06:25

If you retract an entity that has :db.unique/value, that value can't be asserted again?