-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support registration of custom TableProviders through SQL #3310
Comments
Sorry for commenting on closed thread, question for @avantgardnerio and/or @alamb question, should |
@milenkovicm I think that's not a bad idea, and some versions of the PR did exactly that... however I do think there's one choice to be made:
I would be fine either way, but I think the purpose of the |
thanks @avantgardnerio , I believe first option may make more sense, might be easier api to digest. Other small note, as I'm working on a branch where I've added this change Optional may be redundant as empty schema will be provided by context.rs |
FWIW, I would advocate for the presence of an empty schema to be represented differently than the absence of a schema. |
@avantgardnerio do you mean changing |
I meant as a concept in general - not using
vs
|
@avantgardnerio please have a look at #4142 should support what we've discussed. thanks |
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
As a DataFusion / Ballista user, one awesome feature is that I can create custom table providers and register them on the context to support datasources not built into DataFusion itself (e.g. DeltaLake). However, if I make my own server (i.e. Ballista fork or Ballista with plugins) I cannot allow my users to register arbitrary tables at run time through SQL - I need to hard-code those into my app.
Describe the solution you'd like
I would like to extend the
create external table
syntax to allow registration of arbitrary table types.Describe alternatives you've considered
create external table
The text was updated successfully, but these errors were encountered: