apache / apache/hudi

[SUPPORT] file versioning is happening as not expected for cow Tables hudi 0.14.0

Open
#13,502 6 comments 0 reactions 0 assignees View on GitHub
area:table-service type:community-support
Dominant language
Java
Stars
6.2k
Forks
2.5k
Avg merge
2d 8h
Merged PRs (30d)
111

Description

**_Tips before filing an issue_**

- Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)?

- Join the mailing list to engage in conversations and get faster support at dev-subscribe@hudi.apache.org.

- If you have triaged this as a bug, then file an [issue](https://issues.apache.org/jira/projects/HUDI/issues) directly.

**Describe the problem you faced**

A clear and concise description of the problem.

**To Reproduce**

Steps to reproduce the behavior:

1. 3 file version not maintaining using below hudi options running glue jobs

{
'hoodie.datasource.write.table.type': 'COPY_ON_WRITE',
'hoodie.datasource.hive_sync.enable': 'true',
"hoodie.datasource.hive_sync.mode": "hms",
'hoodie.datasource.hive_sync.sync_as_datasource': 'false',
'hoodie.datasource.hive_sync.use_jdbc': 'false',
'hoodie.datasource.hive_sync.support_timestamp': 'true',
'hoodie.index.type': "GLOBAL_SIMPLE",
'hoodie.cleaner.policy': "KEEP_LATEST_FILE_VERSIONS",
# 'hoodie.cleaner.fileversions.retained': "5",
# "hoodie.parquet.max.file.size": 536870912,
# 'hoodie.cleaner.policy.failed.writes': 'LAZY',
'hoodie.write.concurrency.mode': "optimistic_concurrency_control",
'hoodie.write.lock.provider': 'org.apache.hudi.aws.transaction.lock.DynamoDBBasedLockProvider',
'hoodie.write.lock.dynamodb.table': args['LOCK_TABLE_NAME'],
'hoodie.write.lock.dynamodb.billing_mode': 'PAY_PER_REQUEST',
'hoodie.write.lock.dynamodb.region': '{0}'.format(curr_region),
'hoodie.write.lock.dynamodb.endpoint_url': 'dynamodb.{0}.amazonaws.com'.format(curr_region),
'hoodie.insert.shuffle.parallelism': 200,
'hoodie.upsert.shuffle.parallelism': 200,
'hoodie.metadata.index.column.stats.enable': 'true',
'hoodie.clean.automatic': "true",
'hoodie.cleaner.fileversions.retained': "3",
"hoodie.parquet.max.file.size": 30000000,
"hoodie.parquet.small.file.limit": 20000000, # 100 MB
'hoodie.cleaner.policy.failed.writes': 'LAZY',
'hoodie.cleaner.parallelism': 200,
}

![Image](https://github.com/user-attachments/assets/b67a3c3b-0e60-4839-9ed6-a06dbf094a5c)

**Expected behavior**
need to maintain 3 file versions

A clear and concise description of what you expected to happen.

**Environment Description**

* Hudi version :0.14.0

* Spark version : 3.3

* Hive version :

* Hadoop version :

* Storage (HDFS/S3/GCS..) :s3

* Running on Docker? (yes/no) : No

**Additional context**

Add any other context about the problem here.

**Stacktrace**

```Add the stacktrace of the error.```

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Start by reproducing the issue with Hudi 0.14.0, Spark 3.3, S3, and the listed cleaner settings, then inspect how automatic cleaning handles COPY_ON_WRITE tables and file version retention. Done means the table consistently retains the requested three file versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java, spark
Domain
cloud, data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.