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
[Python][C++] Crash when performing join on a table larger than INT32_MAX bytes #36879
changed the title [-]Crash when performing `join` on a table larger than INT32_MAX bytes[/-][+][Python][C++] Crash when performing `join` on a table larger than INT32_MAX bytes[/+]on Jul 26, 2023
This is the same Basic Hash Join / RowEncoder overflow as #54885, but in the build-side payload rather than the keys.
The large_binary columns select Basic Join. Their combined encoded size exceeds its signed 32-bit offset range, even though each column alone is below 2 GiB. Reversing the inputs makes the small table the build side and avoids that accumulation.
Closed as a duplicate of #54885; the underlying bug remains unresolved.
Activity
[-]Crash when performing `join` on a table larger than INT32_MAX bytes[/-][+][Python][C++] Crash when performing `join` on a table larger than INT32_MAX bytes[/+]idailylife commentedon Jan 23, 2024
Is this (#33151) related?
zanmato1984 commentedon Oct 22, 2026
This is the same Basic Hash Join /
RowEncoderoverflow as #54885, but in the build-side payload rather than the keys.The
large_binarycolumns select Basic Join. Their combined encoded size exceeds its signed 32-bit offset range, even though each column alone is below 2 GiB. Reversing the inputs makes the small table the build side and avoids that accumulation.Closed as a duplicate of #54885; the underlying bug remains unresolved.
large_stringkeys near 2gb #54885