Closed westonpace closed 1 week ago
We will have this supported in datafusion-python
43.0.0! As soon as upstream updates, we will make a few small changes to https://github.com/apache/datafusion-python/pull/921 and get that merged in. Then we will be able to support this. Upstream datafusion
43.0.0 is under release review right now.
A stable FFI for table providers! I had no idea. Very cool.
This is similar to #920 but maybe more specific. Lance (https://github.com/lancedb/lance) has a custom table provider and I was interested in using datafusion-python with this table provider. However, I'm not sure there is an easy solution.
I was hoping, in Lance's python bindings, I could just do something like...
Then use this in python as:
Unfortunately, this leads to:
I suspect the problem is that the
SessionContext
linked into lance's python module is different from theSessionContext
linked into datafusion_python's python module.Here's a few thoughts off the top of my head. Maybe there is something easier I am missing however.
A simple, but not ideal, solution is to just add lance as a dependency to datafusion-python. I'm assuming that the datafusion-python project doesn't want 3rd party dependencies however.
The "dataset protocol" never got quite finished but we can kind of use pyarrow datasets as the dataset protocol. This is actually what I've ended up using for the time being. I use register_dataset and
LanceDataset
already duck types as a pyarrow dataset so this works but it's not as flexible.I'm not entirely sure this is possible but it seems the datafusion-federation project may have a way of handling abstract table providers over Substrait. datafusion-python could add datafusion-federation as a dependency to allow a
register_federated
method.