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
This will be necessary for ARROW-11928 since some ExecNodes will be constructed with one or more Expressions. For example FilterNodes will evaluate an Expression against their input batches to produce selection vectors.
This should probably include factoring out dataset-specific considerations such as allowing input batches diverge slightly in schema. Bound Expressions should refer to their parameters by index so that by-name lookup can be avoided.
See discussion in https://docs.google.com/document/d/1AyTdLU-RxA-Gsb9EsYnrQrmqPMOYMfPlWwxRi1Is1tQ
This will be necessary for ARROW-11928 since some ExecNodes will be constructed with one or more Expressions. For example FilterNodes will evaluate an Expression against their input batches to produce selection vectors.
This should probably include factoring out dataset-specific considerations such as allowing input batches diverge slightly in schema. Bound Expressions should refer to their parameters by index so that by-name lookup can be avoided.
Reporter: Ben Kietzman / @bkietz
Assignee: Ben Kietzman / @bkietz
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-11929. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: