We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The BallistaContext.register_table(name,dataframe) method can register any type of dataframe. But when serializing the plan to send it to the scheduler, it will only work if the value wrapped with the DfTableAdapter is a LogicalPlan::TableScan.
BallistaContext.register_table(name,dataframe)
DfTableAdapter
LogicalPlan::TableScan
To Reproduce Steps to reproduce the behavior:
BallistaContext.read_xxx()
BallistaContext.register_table()
Expected behavior Possibilities:
TableProvider
DataFrame
The text was updated successfully, but these errors were encountered:
Note that according to the solution chosen, this will also close #1016
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
The
BallistaContext.register_table(name,dataframe)
method can register any type of dataframe. But when serializing the plan to send it to the scheduler, it will only work if the value wrapped with theDfTableAdapter
is aLogicalPlan::TableScan
.To Reproduce
Steps to reproduce the behavior:
BallistaContext.read_xxx()
methodBallistaContext.register_table()
Expected behavior
Possibilities:
TableProvider
instead ofDataFrame
(just as in Datafusion)DfTableAdapter
before serializationDataFrame
s and implement the unwrapping in DataFusionThe text was updated successfully, but these errors were encountered: