wangzhigang1999 opened a new issue, #11198: URL: https://github.com/apache/paimon/issues/11198
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version master at `f1ffd1369ae6db2438a4c9a98fe4216566e88ccc`. ### Compute Engine PyPaimon, Python 3.7.17, PyArrow 8.0.0 / 9.0.0, Linux x86_64. ### Minimal reproduce step With PyPaimon installed from the commit above and PyArrow 8.0.0 or 9.0.0, construct an S3 FileIO: ```python from pypaimon.common.options import Options from pypaimon.filesystem.pyarrow_file_io import PyArrowFileIO PyArrowFileIO("s3://bucket/table", Options({ "fs.s3.endpoint": "http://127.0.0.1:9000", "fs.s3.region": "us-east-1", "fs.s3.accessKeyId": "test-key", "fs.s3.accessKeySecret": "test-secret", })) ``` Initialization fails before any object read: ```text AttributeError: module 'pyarrow.fs' has no attribute 'AwsStandardS3RetryStrategy' ``` ### What doesn't meet your expectations? PyPaimon allows `pyarrow>=7,<13` on Python 3.7, so S3 client initialization should work with these versions. The PyArrow-backed legacy OSS path fails for the same reason. In `_create_s3_retry_config`, we enable `AwsStandardS3RetryStrategy`, `request_timeout` and `connect_timeout` for PyArrow >=8. These Python APIs were added in PyArrow 10. Removing only the retry strategy still leaves unsupported timeout arguments on 8/9. ### Anything else? Compare the official [Arrow 9 source](https://github.com/apache/arrow/blob/apache-arrow-9.0.0/python/pyarrow/_s3fs.pyx) with [Arrow 10](https://github.com/apache/arrow/blob/apache-arrow-10.0.0/python/pyarrow/_s3fs.pyx). Changing the version guard to >=10 lets older versions use their default S3 settings. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
