HDDS-12321. Add Trino integration user guide - #399
Draft
jojochuang wants to merge 10 commits into
Draft
Conversation
Document Trino with Ozone via the Hive connector, Ranger Docker-style workflows, ozonefs-hadoop3 JAR install, catalog and access-control properties, and operational caveats. Link Trino from the homepage. Use ozone-filesystem-hadoop3 from the ozonefs-hadoop3 module (no ozonefs-hadoop3-client / proto.shaded.prefix). Clarify Hadoop XML and Ranger plugin requirements in-container. Made-with: Cursor
Document HDDS-14056 JAR changes, three-Datanode compose setup, staging path, and fixes found during end-to-end verification with Trino 483 and Ozone 2.2.0. Co-authored-by: Cursor <cursoragent@cursor.com>
Remove outdated client JAR and Ranger-first layout; consolidate into a shorter Docker lab walkthrough with a compact troubleshooting table. Co-authored-by: Cursor <cursoragent@cursor.com>
Add explicit curl/jar commands and docker cp step matching lab verification. Co-authored-by: Cursor <cursoragent@cursor.com>
Add verified s3a setup with Trino 483 native S3 and HMS S3A client configuration; note read/metadata success and INSERT limitation in lab. Co-authored-by: Cursor <cursoragent@cursor.com>
Docusaurus expects slug paths without numeric prefixes for cross-doc links. Co-authored-by: Cursor <cursoragent@cursor.com>
Document S3G INSERT failures, ofs-only core-site.xml for Trino, and shared HMS schema naming when both catalogs are used. Co-authored-by: Cursor <cursoragent@cursor.com>
Avoids HMS name collision with the S3 Gateway lab schema and documents S3AFileSystem errors when querying s3a tables via the ozone catalog. Co-authored-by: Cursor <cursoragent@cursor.com>
Clarify HMS vs Trino config split, bucket URI mapping, hive-site example, and S3 catalog deployment steps. Co-authored-by: Cursor <cursoragent@cursor.com>
Use docker cp for HMS and Trino on macOS, require three Datanodes for INSERT, and document Web UI vs in-container CLI. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use ozone-filesystem-hadoopF3 from the ozonefs-hadoop3 module (no ozonefs-hadoop3-client / proto.shaded.prefix). Clarify Hadoop XML and Ranger plugin requirements in-container.
Made-with: Cursor
What changes were proposed in this pull request?
Document Trino with Ozone via the Hive connector, Ranger Docker-style workflows, ozonefs-hadoop3 JAR install, catalog and access-control properties, and operational caveats. Link Trino from the homepage.
What is the link to the Apache Jira?
https://issues.apache.org/jira/browse/HDDS-12321
How was this patch tested?