flâneur

Publish an incremental scan event during planning · Issue #1711 · apache/iceberg

github.com · 109 words · saved by 1 readers

I can take a look into this. Incremental scan has a ‘from’ and ‘to’ snapshot that needs to be passed to the event as well. @rdsr, @rdblue, please let me know your comments. Thanks. The text was updated successfully, but these errors were encountered: I think we should maintain compatibility in ScanEvent since it is part of the API. I think I favor the first option, to add an IncrementalScanEvent. Sorry, something went wrong. sounds good. I went ahead and created a pr using the first option. Sorry, something went wrong. Add your comment here... We don’t support that file type. Try again with GIF, JPEG, JPG, MOV, MP4, PNG, SVG, WEBM, CPUPROFILE, CSV, DMP, DOCX, FODG, FODP, FODS, FODT, GZ, JSON, JSONC, LOG, MD, ODF, ODG, ODP, ODS, ODT, PATCH, PDF, PPTX, TGZ, TXT, XLS, XLSX or ZIP. Attaching documents requires write permission to this repository. Try again with GIF, JPEG, JPG, MOV, MP4, PNG, SVG, WEBM, CPUPROFILE, CSV, DMP

There is a todo in the IncrementalDataTableScan to publish a incremental scan event. I can take a look into this. Incremental scan has a ‘from’ and ‘to’ snapshot that needs to be passed to the event as well. We can add a new IncrementalScanEvent that has the ‘from’ and ‘to’ snapshot information as well in addition to the projection, filter and tablename info. Or We could enhance the ScanEvent that exists today, although the snapshotId there won’t apply to the Incremental scan event. What is the compatibility guarantees for ScanEvent across releases since it is part of the api folder?…

saved by

related reading