ZENOTME opened a new issue, #1047: URL: https://github.com/apache/iceberg-rust/issues/1047
### Is your feature request related to a problem or challenge? For now, our arrow reader accepts the FileScanTask and returns the RecordBatchStream to the user. After #630, the reader can process the delete file and merge it with the data file, which it's good to ready to use out of the box. However, for some compute engines, they hope to process delete file by themselves so that they can utilize the existing join executor and storage to spill the data. This require to read the delete file directly rather than process the delete file internally. Based on this, I suggest providing different read interface so that it satisfy different requirement: - read: process data and delete file of FileScanTask internally - read_data: read data file of FileScanTask internally - read_pos_delete: read position delete file of FileScanTask and return result directly - read_eq_delete: read equality delete file of FileScanTask and return result directly ### Describe the solution you'd like _No response_ ### Willingness to contribute - [ ] I can contribute to this feature independently - [ ] I would be willing to contribute to this feature with guidance from the Iceberg Rust community - [ ] I cannot contribute to this feature at this time -- 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: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
