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.

Sign up for GitHub

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

Jump to bottom

SQL planner should use TableSource not TableProvider #2346

Closed
andygrove opened this issue Apr 26, 2022 · 0 comments · Fixed by #2569
Closed

SQL planner should use TableSource not TableProvider #2346

andygrove opened this issue Apr 26, 2022 · 0 comments · Fixed by #2569
Labels
enhancement New feature or request

Comments

@andygrove
Copy link
Member

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
SQL planner should use TableSource not TableProvider since there is no need to actually perform scans during planning and this would be a step towards moving the SQL planner into its own crate so we have cleaner dependency management,

Describe the solution you'd like
SQL planner should use TableSource not TableProvider

Describe alternatives you've considered
None

Additional context
None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

LogicalPlanBuilder now uses TableSource instead of TableProvider andygrove/datafusion
1 participant
@andygrove