Skip to content

Conversation

@rdettai
Copy link
Contributor

@rdettai rdettai commented Sep 20, 2021

Which issue does this PR close?

Closes #1027 and Closes #1016.

What changes are included in this PR?

  • Removed the DfTableAdapter wrapper
  • removed dead code from scheduler planner (execution_plan could not be downcasted to DfTableAdapter)
  • unwrap the dataframe into a table provider directly in the register_xx methods

Are there any user-facing changes?

BallistaContext.register_table() takes TableProviders instead of DataFrames.

Copy link
Contributor

@Dandandan Dandandan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks - this definitely makes sense and looks like it simplifies a lot.

Copy link
Member

@houqp houqp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good change, also makes it consistent with what we have in datafusion context.

@houqp houqp added the api change Changes the API exposed to users of the crate label Sep 20, 2021
@houqp houqp changed the title Remove ability to register dataframes on BallistaContext Register tables in BallistaContext using TableProviders instead of Dataframe Sep 20, 2021
@houqp houqp merged commit 843cd93 into apache:master Sep 20, 2021
@rdettai rdettai deleted the register-dataframe branch September 21, 2021 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api change Changes the API exposed to users of the crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ballista register_table does not work with Dataframes that are not TableProviders Avoid creating ExecutionPlan for registered tables in Ballista

3 participants