Clojurians Log v2

@konrad.kuehne is datahike 0.2.2 going to support konserve 0.6.0?

We will add that with another patch release. Once the migrations and GC are established.

👍

It should be compatible though. The interface of konserve is not changing to the outside unless you start to manually hook into the metadata and do not stick to the core.cljc or cache.cljc functions.

@jonpither, @malcolmsparks, @taylor.jeremydavid Hello 🙂

@thegobinath There was recently a discussion about this here: https://github.com/athensresearch/athens/issues/9

Yes, we have schema support similar to Datomic and I think both crux and us care about scalability.

Thanks 🙂

It currently fails because the protocol in 0.6.0 has renamed/changed get-in to just get .

Caused by: java.lang.IllegalAccessError: -get-in does not exist

@whilo @konrad.kuehne I've successfully migrated the konserve-fire to v0.6.0. Only have one question. You mentioned something about encoding the version in the first byte. For the life of me I can't figure out how to encode v0.6.0 and not confuse it with v6.

Actually I have two. I want to add a tests for speediness of the integration. Any idea about the minimum speed of a konserve backend should be?