xtdb 2022-11-28 | Slack Archive

Ben Sless14:11:34

Nice use case I found for xtdb + inspector, set up in a testing environment, ingest all messages from Kafka to the db. Then it can be used for queries over all topics in the environment for tests and visibility

👀 1

💡 1

hairfire22:11:50

I seem to remember executing a query like:

(xt/q (xt/db node)
        '{:find [x]
          :where [[_ x _]]})

back in the early days of CRUX when I was demoing to a co-worker. Now the query fails. Does the query make sense? The intent is to get all the attributes in the DB.

refset23:11:33

Hey Paul 🙂 XT (Crux) has actually never supported wildcard attributes like that, so you can only ever use a keyword literal in the attribute position for a triple clause. However, you can enumerate all the attributes in the db using the attribute-stats API, and you can then use this information programmatically to do things like: https://gist.github.com/refset/93135adcbf41fccab9b641638ab10997

hairfire14:11:02

👍

rickmoynihan13:12:57

I asked a similar question the other week: https://clojurians.slack.com/archives/CG3AM2F7V/p1668687791764809

🙏 1

2022-11-28

Channels