You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
col_summary_tbl() does not accept ibis.expr.types.relations.Table #286
If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.
Description
Describe the bug clearly and concisely.
Putting an ibis.expr.types.relations.Table object into col_summary_tbl() returns TypeError: Expected pandas-like dataframe, Polars dataframe, or Polars lazyframe, got: <class 'pyarrow.lib.RecordBatchReader'> even though documentation states that Ibis's Table objects should be acceptable. I have checked the type of the input into the function.
Reproducible example
Post a minimal reproducible example (MRE) so the maintainer can troubleshoot the problems you identify. A reproducible example is:
Runnable: post enough code and data so any onlooker can create the error on their own computer.
Minimal: reduce runtime wherever possible and remove complicated details that are irrelevant to the issue at hand.
importpointblankaspbimportibisibis.options.interactive=Trueibis_database_table_object=ibis.duckdb.connect("salesforce_contacts.duckdb").table("all_contacts")
print(f"ibis_database_table_object's type is: {type(ibis_database_table_object)}")
pb.col_summary_tbl(data=ibis_database_table_object)
Expected result
I would expect to be able to get a summary of the table.
This is likely because the latest version of duckdb breaks things in the latest ibis (see this issue for some details: ibis-project/ibis#11621).
The solution right here right now is to use the previous stable release of duckdb. Soon, ibis will release with the fix in place, so this situation won’t last too long.
Activity
rich-iannone commentedon Sep 24, 2025
This is likely because the latest version of
duckdbbreaks things in the latestibis(see this issue for some details: ibis-project/ibis#11621).The solution right here right now is to use the previous stable release of
duckdb. Soon,ibiswill release with the fix in place, so this situation won’t last too long.