Joel

>Apple rolls their own DSL for configuration > https://github.com/apple/pkl So I find the niche space of "Configuration languages" like [Jsonnet](https://jsonnet.org/), [Dhall](https://dhall-lang.org/), [Cue](https://cuelang.org/) and now pkl super interesting. I've posted [this...

@inigohidalgo thank you for putting a lot of thought into this - I spent last night reading about [Ibis](https://ibis-project.org/) which I think may be the modern and correct way to...

This is super cool @inigohidalgo - until now SQL has always been a 2nd class citizen in Kedro and this is a huge step forward in terms of usability and...

That's super cool @lostmygithubaccount

So I have 3 cascading questions: 1. Do we do a mega `ibis.IbisDataSet` that supports all back-ends, SQL/DataFrame whatever? 2. If this isn't feasible would separate `ibis.SQLDataset` and `ibis.DataFrameDataset`s make...

Yes @cpcloud we have something like this currently in our [setup.py](https://github.com/kedro-org/kedro-plugins/blob/main/kedro-datasets/setup.py) (sorry, pyproject.toml coming soon!) and the main point I was making is that we don't want to double up.

At this point - shouldn't we just push people towards formats like Iceberg?

I should say your solution is neat and elegant... but do we need to expose this to the user?

I'm for anything that removes the `AbstractVersionedDataset`, I guess the flip side - if we delegate the versioning to some other technology how do we standardise the `kedro run --load-versions=:YYYY-MM-DDThh.mm.ss.sssZ`...

Yeah I suspect if you use versioning in the first place you either need this or `Datacatalog.load({name}, version=...)` to actually interrogate your work. A very quick scan shows it's baked...