GH-33976: [Python] Refactor the internal usage of ExecPlan to use new Acero Declaration/ExecNodeOptions bindings#34401
Conversation
8a9b8c9 to
202859f
Compare
202859f to
b0d4616
Compare
b0d4616 to
b756e92
Compare
b756e92 to
011180f
Compare
|
With the last commit, I renamed |
011180f to
474103e
Compare
| with pytest.raises(pa.ArrowTypeError): | ||
| ep._filter_table( | ||
| t, pc.divide(pc.field("a"), pc.scalar(2)), | ||
| output_type=pa.Table |
There was a problem hiding this comment.
Since we only ever used output_type=pa.Table option for this keyword in _filter_table, I removed the keyword and simplified the tests
AlenkaF
left a comment
There was a problem hiding this comment.
I see nothing obvious missing. The code is hugely optimised and much clearer now so the maintenance of it will benefit big time 👍 Thanks!
|
Benchmark runs are scheduled for baseline = c74540f and contender = 0ead719. 0ead719 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…se new Acero Declaration/ExecNodeOptions bindings (apache#34401) This PR refactors our current custom cython implementation of the Table/Dataset.filter/join/group_by/sort_by methods to use the new bindings for Declaration/ExecNodeOptions (apache#34102). * Issue: apache#33976 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
This PR refactors our current custom cython implementation of the Table/Dataset.filter/join/group_by/sort_by methods to use the new bindings for Declaration/ExecNodeOptions (#34102).