xushiyan commented on code in PR #14192:
URL: https://github.com/apache/hudi/pull/14192#discussion_r2495425129


##########
website/versioned_docs/version-0.14.0/compaction.md:
##########
@@ -13,7 +13,7 @@ not applicable to Copy On Write(COW) tables and only applies 
to MOR tables.
 
 ### Why MOR tables need compaction?
 To understand the significance of compaction in MOR tables, it is helpful to 
understand the MOR table layout first. In Hudi, 
-data is organized in terms of [file 
groups](https://hudi.apache.org/docs/file_layouts/). Each file group in a MOR 
table 
+data is organized in terms of [file groups](file_layouts). Each file group in 
a MOR table 

Review Comment:
   ```suggestion
   data is organized in terms of [file groups](/docs/file_layouts). Each file 
group in a MOR table 
   ```



##########
website/versioned_docs/version-0.14.1/compaction.md:
##########
@@ -13,7 +13,7 @@ not applicable to Copy On Write(COW) tables and only applies 
to MOR tables.
 
 ### Why MOR tables need compaction?
 To understand the significance of compaction in MOR tables, it is helpful to 
understand the MOR table layout first. In Hudi, 
-data is organized in terms of [file 
groups](https://hudi.apache.org/docs/file_layouts/). Each file group in a MOR 
table 
+data is organized in terms of [file groups](file_layouts). Each file group in 
a MOR table 

Review Comment:
   same problem. make sure you get it right about relative path



##########
website/versioned_docs/version-1.0.0/compaction.md:
##########
@@ -13,7 +13,7 @@ not applicable to Copy On Write(COW) tables and only applies 
to MOR tables.
 
 ### Why MOR tables need compaction?
 To understand the significance of compaction in MOR tables, it is helpful to 
understand the MOR table layout first. In Hudi, 
-data is organized in terms of [file 
groups](https://hudi.apache.org/docs/file_layouts/). Each file group in a MOR 
table 
+data is organized in terms of [file groups](storage_layouts). Each file group 
in a MOR table 

Review Comment:
   relative path problem



##########
website/versioned_docs/version-0.15.0/compaction.md:
##########
@@ -13,7 +13,7 @@ not applicable to Copy On Write(COW) tables and only applies 
to MOR tables.
 
 ### Why MOR tables need compaction?
 To understand the significance of compaction in MOR tables, it is helpful to 
understand the MOR table layout first. In Hudi, 
-data is organized in terms of [file 
groups](https://hudi.apache.org/docs/file_layouts/). Each file group in a MOR 
table 
+data is organized in terms of [file groups](file_layouts). Each file group in 
a MOR table 

Review Comment:
   relative path problem



##########
website/versioned_docs/version-1.0.1/compaction.md:
##########
@@ -13,7 +13,7 @@ not applicable to Copy On Write(COW) tables and only applies 
to MOR tables.
 
 ### Why MOR tables need compaction?
 To understand the significance of compaction in MOR tables, it is helpful to 
understand the MOR table layout first. In Hudi, 
-data is organized in terms of [file 
groups](https://hudi.apache.org/docs/file_layouts/). Each file group in a MOR 
table 
+data is organized in terms of [file groups](storage_layouts). Each file group 
in a MOR table 

Review Comment:
   relative path problem



##########
website/versioned_docs/version-0.14.1/s3_hoodie.md:
##########
@@ -88,7 +88,7 @@ AWS glue data libraries are needed if AWS glue data is used
 
 ## AWS S3 Versioned Bucket
 
-With versioned buckets any object deleted creates a [Delete 
Marker](https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html),
 as Hudi cleans up files using [Cleaner 
utility](https://hudi.apache.orghoodie_cleaner) the number of Delete Markers 
increases over time.
+With versioned buckets any object deleted creates a [Delete 
Marker](https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html),
 as Hudi cleans up files using [Cleaner utility](hoodie_cleaner) the number of 
Delete Markers increases over time.

Review Comment:
   relative path problem



##########
website/versioned_docs/version-0.15.0/s3_hoodie.md:
##########
@@ -88,7 +88,7 @@ AWS glue data libraries are needed if AWS glue data is used
 
 ## AWS S3 Versioned Bucket
 
-With versioned buckets any object deleted creates a [Delete 
Marker](https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html),
 as Hudi cleans up files using [Cleaner 
utility](https://hudi.apache.orghoodie_cleaner) the number of Delete Markers 
increases over time.
+With versioned buckets any object deleted creates a [Delete 
Marker](https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html),
 as Hudi cleans up files using [Cleaner utility](hoodie_cleaner) the number of 
Delete Markers increases over time.

Review Comment:
   relative path problem



##########
website/versioned_docs/version-1.0.0/s3_hoodie.md:
##########
@@ -88,7 +88,7 @@ AWS glue data libraries are needed if AWS glue data is used
 
 ## AWS S3 Versioned Bucket
 
-With versioned buckets any object deleted creates a [Delete 
Marker](https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html),
 as Hudi cleans up files using [Cleaner 
utility](https://hudi.apache.orghoodie_cleaner) the number of Delete Markers 
increases over time.
+With versioned buckets any object deleted creates a [Delete 
Marker](https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html),
 as Hudi cleans up files using [Cleaner utility](cleaning) the number of Delete 
Markers increases over time.

Review Comment:
   relative path problem



##########
website/versioned_docs/version-1.0.2/compaction.md:
##########
@@ -13,7 +13,7 @@ not applicable to Copy On Write(COW) tables and only applies 
to MOR tables.
 
 ### Why MOR tables need compaction?
 To understand the significance of compaction in MOR tables, it is helpful to 
understand the MOR table layout first. In Hudi, 
-data is organized in terms of [file 
groups](https://hudi.apache.org/docs/file_layouts/). Each file group in a MOR 
table 
+data is organized in terms of [file groups](/docs/storage_layouts/). Each file 
group in a MOR table 

Review Comment:
   this is the correct change. why are other relative path changes not 
following this?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to