westonpace commented on PR #33770: URL: https://github.com/apache/arrow/pull/33770#issuecomment-1400632307
> So I don't know why you need the projection expression at all, unless it is aspirational/future-looking for some time when the projection can be pushed down and handled by the file readers or whatever. > We can ship this but I wonder if it wouldn't be better just to remove this projection interface and only accept a schema, which may filter out top-level fields only, no other projection. It's less aspirational and more historical. This comes from the pre-ExecPlan days when the scanner was "scan->filter->project". The new scan node API simply accepts a vector of field refs. However, it should support those field refs being nested refs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
