[
https://issues.apache.org/jira/browse/HUDI-9711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiyan Xu updated HUDI-9711:
----------------------------
Description:
Incremental timestamps should support taking in `yyyyMMddHHmmssSSS`, or ISO
timestamps like `2025-01-02` or `2025-01-02T03:04:56.789`, etc, or epoch
seconds or mills.
Currently, random numbers like 42 can be passed to it and go through.
It should validate the input and fail as soon as the input is not in the
expected format. Same goes for time-travel query.
[https://github.com/apache/hudi-rs] has implemented this:
!Screenshot 2025-08-13 at 2.00.15 PM.png!
was:
Incremental timestamps should support taking in `yyyyMMddHHmmssSSS`, or ISO
timestamps like `2025-01-02` or `2025-01-02T03:04:56.789`, etc, or epoch
seconds or mills.
Currently, random numbers like 42 can be passed to it and go through.
It should validate the input and fail as soon as the input is not in the
expected format. Same goes for time-travel query.
h1. *List of supported formats:*
!Screenshot 2025-08-13 at 2.00.15 PM.png!
> Incremental start/end time parameters do not have validation
> ------------------------------------------------------------
>
> Key: HUDI-9711
> URL: https://issues.apache.org/jira/browse/HUDI-9711
> Project: Apache Hudi
> Issue Type: Bug
> Components: reader-core
> Reporter: Shiyan Xu
> Priority: Major
> Fix For: 1.1.0
>
> Attachments: Screenshot 2025-08-13 at 2.00.15 PM.png
>
>
> Incremental timestamps should support taking in `yyyyMMddHHmmssSSS`, or ISO
> timestamps like `2025-01-02` or `2025-01-02T03:04:56.789`, etc, or epoch
> seconds or mills.
> Currently, random numbers like 42 can be passed to it and go through.
> It should validate the input and fail as soon as the input is not in the
> expected format. Same goes for time-travel query.
> [https://github.com/apache/hudi-rs] has implemented this:
> !Screenshot 2025-08-13 at 2.00.15 PM.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
