Jeremy Taylor

Hi @tkovis I've not been able to reproduce this so far. To help rule things out, can you confirm which OS & JVM you were using here please? For (my...

Thanks for the additional info. Have you got the ability to check this behaviour on Linux? It _might_ be a macOS-specific issue. I'll also try to find a way to...

Looking at a `LEFT OUTER JOIN` example first: ```clojure (let [q (str "SELECT * FROM PERSON\n" " INNER JOIN PLANET ON PERSON.PLANET = PLANET.NAME")] ``` We can certainly already push...

I believe the issue here is that the we're "storing" `nil` values for each of the entries we're unindexing: https://github.com/juxt/crux/blob/63e99523b73478490618c99760f3e28e2e1acf33/crux-core/src/crux/kv/index_store.clj#L1045 And then almost immediately filtering out all those `nil` values,...

One workaround (for 1.4.0 and below) is to add extra dummy clauses so that the relevant lvar (logic variable) is more frequent. E.g. ``` range-test=> (def q4a {:find '[e] #_=>...

There are still cases where range constraints aren't being promoted early enough in the join order when they could be (e.g. at least hypothetically, if XT kept useful histogram index...

Also worth noting: - this could be a pre-requisite for enabling cryptographic proof of immutability by storing signatures alongside the transactions. - important for data lineage use-cases.

Also a pre-requisite for end-to-end integrity. Related: https://github.com/CorfuDB/CorfuDB/wiki/Argument-for-end-to-end-data-integrity > Both data + checksum are included in the Corfu log write API. The server can refuse to store data that was...

This could be per op and, independently, per tx.

Thank you for writing up and sharing your approach @piotr-yuxuan :pray: it's quite elegant in that it bypasses some of the storage overhead involved in creating additional metadata documents (natural...