Skip to content
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

Plans with tables from TableProviderFactorys can't be serialized #3906

Closed
avantgardnerio opened this issue Oct 20, 2022 · 0 comments · Fixed by #3907
Closed

Plans with tables from TableProviderFactorys can't be serialized #3906

avantgardnerio opened this issue Oct 20, 2022 · 0 comments · Fixed by #3907
Labels
enhancement New feature or request

Comments

@avantgardnerio
Copy link
Contributor

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

We recently add TableProviderFactorys to allow registration of tables by users at run time (i.e. CREATE EXTERNAL TABLE dt STORED AS DELTATABLE). However, the resulting logical plans (select * from dt) can't be shipped between nodes (i.e. ballista client & scheduler) due to lack of ability to serde them.

Describe the solution you'd like

  1. Create a CustomTable provider that contains the information necessary to reify the table on a different node (as long as it has the same TableProviderFactory registered).
  2. Add serde logic to make use of the CustomTable

Describe alternatives you've considered

It's all pretty confusing, but I think this is the way forward for logical plans to be extendable by 3rd parties at runtime. I'm open to other suggestions though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant