thswlsqls opened a new issue, #9557: URL: https://github.com/apache/paimon/issues/9557
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ 2788fe596 (2.1-SNAPSHOT) **Compute Engine** Engine-agnostic — the failure is in the `vortex` read path, reached by any engine that pushes filters down. **Minimal reproduce step** In `VortexPredicateConverterTest`, use the existing `roundTrip(...)` helper to write a single `DATE` column (epoch days 10, 20, 30) and read it back with `greaterOrEqual(0, 20)` pushed down. The read throws: ``` java.io.IOException: [errno 22] External error: Cannot compare scalars with incompatible types: vortex.date[days](i32?) and i32 ``` `TIMESTAMP(0)` (`vortex.timestamp[s]` vs `vortex.timestamp[ms]`) and `TIMESTAMP_LTZ(0)` fail the same way. **What doesn't meet your expectations?** Expected: the filter is applied and matching rows are returned. Actual: the whole scan fails. `VortexPredicateConverter.toLiteral()` emits a plain `i32` for `DATE` (grouped with `case INTEGER:`), and `toTimestampLiteral()` emits MILLISECONDS for precision 0 (routed into the `precision <= 3` branch). The writer records those columns as `date[days]` / `timestamp[s]` — `ArrowFieldTypeConversion.getTimeUnit()` maps precision 0 to SECOND — and Vortex does not implicitly cast. `Expression.literalDate` and `TimeUnit.SECONDS`/`DAYS` already exist in `paimon-vortex-jni` but are unused. **Anything else?** N/A **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]
