taowenjun opened a new issue, #13086: URL: https://github.com/apache/seatunnel/issues/13086
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened There are two problems with ZSTD-compressed ORC files: 1. Reading an ORC file compressed with ZSTD fails with: ```text java.lang.IllegalArgumentException: Unknown compression ``` 2. Writing ORC with `compress_codec = "ZSTD"` silently produces uncompressed files. The resulting ORC footer reports `NONE` instead of `ZSTD`. The current ORC dependency is version 1.5.6, which does not support ZSTD. Additionally, `CompressFormat.ZSTD` maps to ORC `CompressionKind.NONE`. ### SeaTunnel Version Community `dev`, based on commit: `b434d2e4f46807a82b0cf4b1a6b52c1e88fd0532` The read failure was also observed in a SeaTunnel 2.3.13 deployment using Hive source to read ZSTD-compressed ORC files. ### SeaTunnel Config ```conf Relevant sink configuration: file_format_type = "ORC" compress_codec = "ZSTD" For the read case, use Hive source to read an existing ORC table containing ZSTD-compressed files. ``` ### Running Command ```shell Submit the configured job using the corresponding SeaTunnel engine launcher. The problem can also be reproduced through the ORC reader and writer unit tests. ``` ### Error Exception ```log java.lang.IllegalArgumentException: Unknown compression Writing does not throw an exception, but the generated ORC footer reports: compression=NONE ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
