An example of using the StarRocks Iceberg engine with Data Catalog

[jcockhren]

Summary

I've tested the R2 Data Catalog service with multiple Iceberg engines (over REST). I found that StarRocks supports basic reads and writes, as well as snapshot management! Determining the correct properties to connect from StarRocks required some trial and error, so I thought it would be helpful to add this information to help others get started quickly.

I didn't create an issue b/c this is strictly an addition of a new example and seems straightforward enough. I followed the style and pattern used for the other Iceberg engine examples.

Documentation checklist

• [x] The documentation style guide has been adhered to.
• [ ] If a larger change - such as adding a new page, an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• [ ] Files which have changed name or location have been allocated redirects.

[hyperlint-ai-deprecated[bot]]

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

---

PR Change Summary

Added an example of using the StarRocks Iceberg engine with the R2 Data Catalog to facilitate user onboarding and provide clear instructions for setup and usage.

• Introduced a new example for connecting StarRocks with R2 Data Catalog.
• Provided detailed prerequisites for setting up StarRocks and R2 integration.
• Included SQL commands for creating an Iceberg catalog and managing databases.

Added Files

• src/content/docs/r2/data-catalog/config-examples/starrocks.mdx

---

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

[jcockhren]

I'm tagging ya'll for a review because the bot told me to. 😄

@elithrar @jonesphillip @harshil1712 @aninibread @Oxyjun

[jcockhren]

Hey, please review when you get a chance. Thanks!

I'm tagging ya'll for a review because the bot told me to. 😄

@elithrar @jonesphillip @harshil1712 @aninibread @Oxyjun

[holopin-bot[bot]]

Congratulations @jcockhren, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmdr8qyy7003707k479affb4l

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!

[Oxyjun]

Hey, please review when you get a chance. Thanks!

I'm tagging ya'll for a review because the bot told me to. 😄 @elithrar @jonesphillip @harshil1712 @aninibread @Oxyjun

Thank you for waiting on us @jcockhren , and thanks for the PR! 😄