CryoThrust opened a new pull request, #12744: URL: https://github.com/apache/seatunnel/pull/12744
### Purpose of this pull request Fixes #12743. The InfluxDB sink treats generated epoch-millisecond values as if they were in the configured `epoch` unit. With the default nanosecond precision, a `TIMESTAMP` value of `2025-01-02T03:04:05.123` is written near 1970. The same mismatch affects processing time when `key_time` is omitted. Pass `MILLISECONDS` to `Point.Builder.time` for those two paths, so the client can convert the actual instant when generating line protocol. Explicit `BIGINT` and numeric `STRING` timestamps still use the configured unit. Update the English and Chinese `key_time` documentation to explain this distinction. ### Does this PR introduce any user-facing change? Generated timestamps now represent their actual time under all supported precisions. Option names/defaults and explicit numeric timestamp behavior are unchanged. Previously written timestamps are not migrated. This is independent of #12741, which fixes null timestamps, retention policy and flush retries. It changes two different unit assignments and adds a separate test class. ### How was this patch tested? On JDK 11: ```shell ./mvnw -pl seatunnel-connectors-v2/connector-influxdb spotless:apply test ./mvnw -pl seatunnel-connectors-v2/connector-influxdb -DskipTests verify ``` - The 24-case regression checks processing time, UTC `TIMESTAMP`, and explicit numeric/string timestamps across all six supported precisions. On unchanged production code, 10 cases fail and 14 pass; with the fix, all 24 pass. - The complete InfluxDB module suite passes: **63 tests, no failures, errors or skips**. - Spotless, Checkstyle, module packaging/verification and `git diff --check` pass. - No live InfluxDB integration or engine E2E test was run. Tests inspect the real client's generated line protocol. ### Check list - [x] English and Chinese documentation updated. - [x] Regression tests added and executed. - [x] No new dependencies or binary packages. -- 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]
