Describe the bug
From a query like select col_a, col_b from table limit N we should apply the same logic as we currently have for this query select * from table limit N in order to just returns needed data and avoid OOM.
Expected behavior
A query using only a Limit and a Projection plan should be optimized.
----For BlazingSQL Developers----Suspected source of the issue
Describe the bug From a query like
select col_a, col_b from table limit N
we should apply the same logic as we currently have for this queryselect * from table limit N
in order to just returns needed data and avoid OOM.Expected behavior A query using only a Limit and a Projection plan should be optimized.
----For BlazingSQL Developers---- Suspected source of the issue