Hey @ULS5BHEUR the HTTP server also supports application/edn and application/transit+json as content types, which should preserve various types end-to-end. Have you observed some unwanted coercion?

Haven't tried transit before, will take a look, thx for pointing me the way to explore 🙏:skin-tone-2:

no problem! for reference, the xtdb-http-client module uses application/edn https://github.com/xtdb/xtdb/blob/7e9c5bf1e62f9f34060065885d9eadf0fe5c4888/modules/http-client/src/xtdb/remote_api_client.clj#L84

My requirement is integrating xtdb with a Ruby app, that's why can't use any of the Clojure client 😅

maybe JRuby + interop is an option...? 😅

I’d like to go that path if I can, but fixing gems compatibility is much more troublesome than using plain http api call to xtdb 😜

we also have another option to use rpc call through the message broker, but for prove of concept prototype, http api is good enough at the moment 🤞:skin-tone-2:

when I switch to post using transit body, I keep getting the invalid-tx-op error from the server the exact same body param post using json is fine, absolutely no clue what’s missing :thinking_face: > { > “errorKey”: “invalid-tx-op”, > “errorType”: “illegal-argument”, > “message”: “invalid tx-op: Invalid tx op”, > “op”: [ > “put”, > { > “name”: “testing”, > “xt/id”: “testing” > } > ] > }

oh I finally figure out why, when I use transit+json, the encoding body must use edn syntax instead, with put replaced by :xtdb.api/put etc 🤞:skin-tone-2:

Ah yep, that'll do it 🙂

The doc-store always stores documents as-is (though hypothetically a doc-store implementation could perform diffing under the hood - none do today), but most things in the local KV indexes on the node are deduplicated already, at least for top-level AVs. Changes to deeply nested values don't get processed as diffs, but might still benefit from RocksDB compression

Hey @U0J3J79FE In case you've not spotted this already - it isn't particularly detailed, and is probably worthy of refreshing, but hopefully is of some use: https://docs.xtdb.com/resources/faq/#comparisons