stevenzwu commented on PR #7217: URL: https://github.com/apache/iceberg/pull/7217#issuecomment-1491224830
@gong it may work for you for your use cases. but I don't think we would adopt this change as a generally applicable solution. we can live out the hard-coded threshold for now. Capping the number of concurrent writers can help with limit the memory footprint. But it will create another serious problem. Now sink can open and close small files all the time. 2 GB memory footprint is really not that big for Parquet writer. you may just want to increase the memory allocation. you can also reduce the Parquet row group size to reduce memory footprint. or switch to Avro file format to reduce memory footprint. if you have bucket partitioning, you can try out this PR that my colleague created recently: https://github.com/apache/iceberg/pull/7161 We are also working on a more general range partitioner that can work with skewed distributions (like event time): https://github.com/apache/iceberg/issues/6303 -- 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]
