Open drin opened 3 weeks ago
I'm not sure if this is actually a bug or if something I used to do is no longer valid.
Note that this code was working prior to the large ibis rewrite, but I have tried to update to latest version of ibis and dropping the use of ibis_conn = ibis.pandas.connect({})
. Now, instead of getting a pyarrow table via ibis_conn.table()
I'm using ibis.memtable(<pyarrow.Table>, name='some_name')
.
If any other context is needed on this, please let me know!
Can you please make the reproducer copypastable?
sure, I can do that by end of day tomorrow.
What happened?
When executing the following function chain (pseudocode):
The error I get is:
The first
outer_join
results in an ibis.Table (<class 'ibis.expr.types.relations.Table'>
), and I would expect the chain to continually produce an ibis.Table.Note that I am actually doing this in a loop as seen here (though the code I'm executing has been updated to use just
ibis.table
instead of a pandas connection).What version of ibis are you using?
python 3.12.7 (
Python 3.12.7 (main, Oct 1 2024, 02:05:46) [Clang 16.0.0 (clang-1600.0.26.3)] on darwin
) ibis-framework[duckdb]==9.5.0What backend(s) are you using, if any?
DuckDB
Relevant log output (pdb excerpts)
I am able to successfully run one iteration of
outer_join
as follows:convenience function:
Debugging (left_table):
Debugging (right_table):
Debugging (result):
Then, a second iteration throws the error, as follows.
Debugging (t3):
The actual error:
Code of Conduct