GitHub user lidavidm added a comment to the discussion: Proposal: ADBC file drivers with pluggable storage
Ok, I guess this could work as an ADBC driver. It could also work as its own spec. I'm a bit agnostic to it so long as implementors/users are happy. > A way to pass a file-system object to a database. A well-known option is enough for prototypes; a dedicated, versioned entry point is likely the long-term answer. I think we'd want a way to pass the entire driver manager to a driver, perhaps? So it could use the registry and load any file drivers (without having to embed its own driver manager)? Note that Spark also has a proposal for native (JNI/FFM) data sources: https://github.com/apache/spark/pull/59313 The filesystem API seems reasonable at a first glance. We could probably compare notes with/steal inspiration from OpenDAL and Arrow Filesystems though it looks similar to the latter off the top of my head. GitHub link: https://github.com/apache/arrow-adbc/discussions/4877#discussioncomment-18896153 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
