dentiny opened a new issue, #1288: URL: https://github.com/apache/iceberg-rust/issues/1288
### Is your feature request related to a problem or challenge? Hi team, checking the [spec](https://iceberg.apache.org/docs/latest/configuration/#table-behavior-properties), I found there're actually timeout requirements for operations. Take "commit.retry.total-timeout-ms" as an example, my understanding is, it's the timeout we should respect when `transaction::commit` should respect. But I don't see any "timeout" or "commit.retry.total-timeout-ms" in the code; I'm wondering if we should and could support that? ### Describe the solution you'd like Asked chatgpt, seems we could set timeout via ```rust use std::time::Duration; use tokio::time; async fn my_async_function() -> Result<(), &'static str> { // Simulate some work tokio::time::sleep(Duration::from_secs(2)).await; Ok(()) } #[tokio::main] async fn main() { let result = time::timeout( Duration::from_secs(1), my_async_function() ).await; // other code } ``` On retry, `tokio-retry` seems to be helpful: https://docs.rs/tokio-retry/latest/tokio_retry/ ### Willingness to contribute I would be willing to contribute to this feature with guidance from the Iceberg Rust community -- 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
