Skip to content

docs: create regression warnings for timestamp issue #14100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
jonvex wants to merge 1 commit into
base: asf-site
Choose a base branch
from
Draft

docs: create regression warnings for timestamp issue #14100

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions website/releases/release-0.14.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,14 @@ It can silently ingest duplicates if table is upgraded from previous versions.
Avoid upgrading any existing table to 0.14.1 if you are using ComplexKeyGenerator with single field as record key and multiple partition fields.
:::

We discovered a regression in Hudi 0.14.1 release related to ingestion of timestamp logical types using HoodieDeltaStreamer/HoodieStreamer.
For timestamp-millis type it will be labeled as timestamp-micros in the parquet and table schemas. For local-timestamp-millis and local-timestamp-micros
they will just be longs with no logical type label.

:::tip
Avoid upgrading any existing table to 0.14.1 if you are using HoodieDeltaStreamer/HoodieStreamer and your table has timestamp-miliis, local-timestamp-millis, or local-timestamp-micros
Copy link
Contributor

@nsivabalan nsivabalan Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

local-timestamp-millis and local0-timestamp-micros is not a regression right?
all previous versions of hudi only renders it as long.
So, why call it out.

:::

## Raw Release Notes

The raw release notes are available [here](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12353493)
Expand Down
8 changes: 8 additions & 0 deletions website/releases/release-0.15.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -326,6 +326,14 @@ it may silently ingest duplicate records.
Avoid upgrading any existing table to 0.14.1 and 0.15.0 from any prior version if you are using ComplexKeyGenerator with single field as record key and multiple partition fields.
:::

The Hudi 0.15.0 release introduces a regression related to ingestion of timestamp logical types using HoodieDeltaStreamer/HoodieStreamer. This issue was also present in version 0.14.1.
For timestamp-millis type it will be labeled as timestamp-micros in the parquet and table schemas. For local-timestamp-millis and local-timestamp-micros
they will just be longs with no logical type label.

:::tip
Avoid upgrading any existing table to 0.14.1 and 0.15.0 from any prior version if you are using HoodieDeltaStreamer/HoodieStreamer and your table has timestamp-miliis, local-timestamp-millis, or local-timestamp-micros
:::

## Raw Release Notes

The raw release notes are
Expand Down
3 changes: 3 additions & 0 deletions website/releases/release-1.0.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,9 @@ experience the new features and enhancements.
- We discovered a regression in Hudi 1.0.0 release for backwards compatible writer for MOR table.
It can silently deletes committed data after upgrade when new data is ingested to the table.
- We also have a ComplexKeyGenerator related regression reported [here](release-0.14.1#known-regressions). Please refrain from migrating, if you have single field as record key and multiple fields as partition fields.
- The Hudi 1.0.0 release introduces a regression related to ingestion of timestamp logical types using HoodieDeltaStreamer/HoodieStreamer. This issue was also present in version 0.15.0 and 0.14.1.
For timestamp-millis type it will be labeled as timestamp-micros in the parquet and table schemas. For local-timestamp-millis and local-timestamp-micros
they will just be longs with no logical type label.

:::tip
Avoid upgrading any existing table to 1.0.0 if any of the above scenario matches your workload. Incase of backwards compatible writer for MOR table, you are good to upgrade to 1.0.2 release.
Expand Down
6 changes: 6 additions & 0 deletions website/releases/release-1.0.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,12 @@ We have a ComplexKeyGenerator related regression reported [here](release-0.14.1#
Avoid upgrading any existing table to 1.0.1 if you are using ComplexKeyGenerator with single record key configured.
:::

We have a HoodieStreamer timestamp logical types related regression reported [here](release-0.14.1#known-regressions). Please refrain from migrating, if you ingest with HoodieDeltaStreamer/HoodieStreamer and your table has timestamp-miliis, local-timestamp-millis, or local-timestamp-micros.

:::tip
Avoid upgrading any existing table to 1.0.1 if you ingest with HoodieDeltaStreamer/HoodieStreamer and your table has timestamp-miliis, local-timestamp-millis, or local-timestamp-micros.
:::

## Raw Release Notes

The raw release notes are available [here](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12355195)
Expand Down
6 changes: 6 additions & 0 deletions website/releases/release-1.0.2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,12 @@ We have a ComplexKeyGenerator related regression reported [here](release-0.14.1#
Avoid upgrading any existing table to 1.0.2 if you are using ComplexKeyGenerator with single record key configured.
:::

We have a HoodieStreamer timestamp logical types related regression reported [here](release-0.14.1#known-regressions). Please refrain from migrating, if you ingest with HoodieDeltaStreamer/HoodieStreamer and your table has timestamp-miliis, local-timestamp-millis, or local-timestamp-micros.

:::tip
Avoid upgrading any existing table to 1.0.2 if you ingest with HoodieDeltaStreamer/HoodieStreamer and your table has timestamp-miliis, local-timestamp-millis, or local-timestamp-micros.
:::

## Raw Release Notes

The raw release notes are available [here](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12355558)
Expand Down