fix(docs): Update link in Hudi documentation to RFC-44

[Joe-Abraham]

Description

Ensure that the Hudi RFC details are accurately documented.

Motivation and Context

Ensure that the Hudi RFC details are accurately documented.

Impact

NA

Test Plan

NA

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

Release Notes

== NO RELEASE NOTE ==

Summary by Sourcery

Documentation:

• Correct the Hudi RFC reference in the connector documentation to point to the appropriate RFC entry.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Hudi connector documentation to point to the correct RFC-44 reference/link for Hudi RFC details.

File-Level Changes

Change	Details	Files
Update the Hudi connector docs to reference the correct RFC-44 documentation link for Hudi.	Adjust the RFC reference text and/or URL in the Hudi connector documentation so it points to RFC-44 Ensure the surrounding description of the Hudi RFC details remains accurate and consistent with the new RFC reference	presto-docs/src/main/sphinx/connector/hudi.rst

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `presto-docs/src/main/sphinx/connector/hudi.rst:9` </location>
<code_context>
 The Hudi connector enables querying `Hudi <https://hudi.apache.org/docs/overview/>`_ tables
 synced to Hive metastore. The connector usesthe metastore only to track partition locations.
 It makes use of the underlying Hudi filesystem and input formats to list data files. To learn
-more about the design of the connector, please check out `RFC-40 <https://github.com/apache/hu
</code_context>

<issue_to_address>
**issue (typo):** Missing space in "usesthe"; should be "uses the".

In that sentence, insert a space so it reads "uses the metastore only to track partition locations."

```suggestion
synced to Hive metastore. The connector uses the metastore only to track partition locations.
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): Missing space in "usesthe"; should be "uses the".

In that sentence, insert a space so it reads "uses the metastore only to track partition locations."

Suggested change

	synced to Hive metastore. The connector usesthe metastore only to track partition locations.
	synced to Hive metastore. The connector uses the metastore only to track partition locations.

[steveburnett]

LGTM! (docs)

Pull branch, local doc build, looks good. Thanks for catching this!

[steveburnett]

Please edit the PR title to pass the required failing test. Maybe something like:

fix(docs): Update link in Hudi documentation to RFC-44

When the failing test is passed, this PR is ready to merge. Thanks!

[Joe-Abraham]

@steveburnett Thank you for the feedback. I’ve also updated the PR title, and all CI checks have passed.