Treasure Data Status

Resolved: The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026.

Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly.

We apologize for the inconvenience and thank you for your patience.

Monitoring: We have deployed a fix for Amazon S3 Parquet imports loading date and time columns as text. New import jobs load these columns as numbers (long), as before October 13, 2026. We are monitoring to ensure stability.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are deploying a fix.

Until the fix is deployed, affected import jobs continue to complete with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are implementing a fix.

Until the fix is deployed, affected import jobs continue to complete successfully with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 1 hour.

Identified: Since October 13, 2026 02:00 UTC, some import jobs that read Parquet files from Amazon S3 complete successfully but load date and time columns as text (string) instead of numbers (long). If the destination table already defines these columns as long, the imported values are empty (NULL).

Only columns stored with a date or time type in the Parquet file are affected. Other columns and other data connectors are not affected.

We have identified the cause, a change introduced in the October 13 release, and are preparing a fix. We are assessing the full scope of impact. We will provide an update in 30 minutes.

Resolved: The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026.

Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly.

We apologize for the inconvenience and thank you for your patience.

Monitoring: We have deployed a fix for Amazon S3 Parquet imports loading date and time columns as text. New import jobs load these columns as numbers (long), as before October 13, 2026. We are monitoring to ensure stability.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are deploying a fix.

Until the fix is deployed, affected import jobs continue to complete with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are implementing a fix.

Until the fix is deployed, affected import jobs continue to complete successfully with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 1 hour.

Identified: Since October 13, 2026 02:00 UTC, some import jobs that read Parquet files from Amazon S3 complete successfully but load date and time columns as text (string) instead of numbers (long). If the destination table already defines these columns as long, the imported values are empty (NULL).

Only columns stored with a date or time type in the Parquet file are affected. Other columns and other data connectors are not affected.

We have identified the cause, a change introduced in the October 13 release, and are preparing a fix. We are assessing the full scope of impact. We will provide an update in 30 minutes.

Resolved: The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026.

Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly.

We apologize for the inconvenience and thank you for your patience.

Monitoring: We have deployed a fix for Amazon S3 Parquet imports loading date and time columns as text. New import jobs load these columns as numbers (long), as before October 13, 2026. We are monitoring to ensure stability.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are deploying a fix.

Until the fix is deployed, affected import jobs continue to complete with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are implementing a fix.

Until the fix is deployed, affected import jobs continue to complete successfully with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 1 hour.

Identified: Since October 13, 2026 02:00 UTC, some import jobs that read Parquet files from Amazon S3 complete successfully but load date and time columns as text (string) instead of numbers (long). If the destination table already defines these columns as long, the imported values are empty (NULL).

Only columns stored with a date or time type in the Parquet file are affected. Other columns and other data connectors are not affected.

We have identified the cause, a change introduced in the October 13 release, and are preparing a fix. We are assessing the full scope of impact. We will provide an update in 30 minutes.

Resolved: The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026.

Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly.

We apologize for the inconvenience and thank you for your patience.

Monitoring: We have deployed a fix for Amazon S3 Parquet imports loading date and time columns as text. New import jobs load these columns as numbers (long), as before October 13, 2026. We are monitoring to ensure stability.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are deploying a fix.

Until the fix is deployed, affected import jobs continue to complete with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 30 minutes.

Identified: We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are implementing a fix.

Until the fix is deployed, affected import jobs continue to complete successfully with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period.

We will provide an update in 1 hour.

Identified: Since October 13, 2026 02:00 UTC, some import jobs that read Parquet files from Amazon S3 complete successfully but load date and time columns as text (string) instead of numbers (long). If the destination table already defines these columns as long, the imported values are empty (NULL).

Only columns stored with a date or time type in the Parquet file are affected. Other columns and other data connectors are not affected.

We have identified the cause, a change introduced in the October 13 release, and are preparing a fix. We are assessing the full scope of impact. We will provide an update in 30 minutes.