Copilot commented on code in PR #17616: URL: https://github.com/apache/hudi/pull/17616#discussion_r2625393399
########## website/docs/concurrency_control.md: ########## @@ -244,7 +244,7 @@ The `NON_BLOCKING_CONCURRENCY_CONTROL` offers the same set of guarantees as ment explicit locks for serializing the writes. Lock is only needed for writing the commit metadata to the Hudi timeline. The completion time for the commits reflects the serialization order and file slicing is done based on completion time. Multiple writers can operate on the table with non-blocking conflict resolution. The writers can write into the same -file group with the conflicts resolved automatically by the query reader and the compactor. It works for compaction and ingestion, and we can see an example of that with [Flink writers](sql_dml#non-blocking-concurrency-control-experimental). +file group with the conflicts resolved automatically by the query reader and the compactor. It works for compaction and ingestion, and we can see an example of that with [Flink writers](../sql_dml#non-blocking-concurrency-control-experimental). Review Comment: The link to sql_dml should not use the relative path prefix '../' since both concurrency_control.md and sql_dml.md are in the same directory (website/docs/). The '../' prefix would incorrectly navigate to the parent directory. The link should be 'sql_dml#non-blocking-concurrency-control-experimental' without the '../' prefix, consistent with other internal links in this file (e.g., line 38 uses 'configurations#LOCK'). ```suggestion file group with the conflicts resolved automatically by the query reader and the compactor. It works for compaction and ingestion, and we can see an example of that with [Flink writers](sql_dml#non-blocking-concurrency-control-experimental). ``` -- 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]
