andygrove commented on code in PR #5298: URL: https://github.com/apache/datafusion-comet/pull/5298#discussion_r3737868842
########## docs/source/user-guide/latest/iceberg-writes.md: ########## @@ -95,3 +98,84 @@ The rewrite is skipped — and the write runs through Spark's stock combined ope In every fallback case the write is planned as if Comet were absent; there is no correctness trade-off, only no plan change. + +## Native Parquet write eligibility + +A planned follow-up replaces the `IcebergWrite` operator's per-task Parquet write with Review Comment: Talking about a planned follow-up here is confusing to me. Is this PR the planned follow-up, or should this link to an issue? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
