apache / apache/paimon

[Bug] When writing a partitioned table for Paimon using Flink SQL and storing the table on HDFS, the partition directory name on HDFS is displayed abnormally. For example, it shows as SCAN_DATE=19415 instead of the correct format of SCAN_DATE=2023-03-01, where SCAN_DATE is of type date.

Open
#773 4 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
3.4k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
396

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/incubator-paimon/issues) and found nothing similar.

### Paimon version

paimon-flink-1.15-0.4-20230330.002117-12.jar

### Compute Engine

flink1.15.3

### Minimal reproduce step

When writing a partitioned table for Paimon using Flink SQL and storing the table on HDFS, the partition directory name on HDFS is displayed abnormally. For example, it shows as SCAN_DATE=19415 instead of the correct format of SCAN_DATE=2023-03-01, where SCAN_DATE is of type date.

### What doesn't meet your expectations?

When writing a partitioned table for Paimon using Flink SQL and storing the table on HDFS, the partition directory name on HDFS is displayed abnormally. For example, it shows as SCAN_DATE=19415 instead of the correct format of SCAN_DATE=2023-03-01, where SCAN_DATE is of type date.

### Anything else?

_No response_

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Reproduce the partitioned-table write with Flink SQL on HDFS using a DATE partition, then trace the partition-path formatting entry point. Done means the HDFS directory uses SCAN_DATE=2023-03-01 rather than the numeric value 19415.

Written by the indexing model from the issue text.

Assessment

Tech stack
hadoop, java
Domain
data-engineering, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.