-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#4962] feat(trino-connector): Support the Trino cascading connector #4935
Conversation
Normally, the directory location is `Trino-server-<version>/plugin`, and the directory contains other catalogs used by Trino. | ||
|
||
Ensure that the `plugin` directory contains `gravitino` and | ||
`trino` subdirectories. Two Trino clusters need to be deployed on machines with hostnames `c1-trino` and `c2-trino`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two Trino clusters need to be deployed on machines with hostnames
c1-trino
andc2-trino
.
I believe what you want to express is that Assuming the hostnames of the machines in which the two Trino cluster deployed are
c1-trinoand
c2-trino``.
The hostname should not necessarily be c1-trino
and c2-trino
, so other name is okay, is that right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
```bash | ||
docker run --name c1-trino -d -p 8080:8080 <image-name> -v `gravitino-trino-connector-<version>`:/usr/lib/trino/plugin/gravitino | ||
-v `gravitino-trino-cascading-connector-<version>`:/usr/lib/trino/plugin/trino | ||
``` | ||
|
||
To start Trino on the host `c2-trino` and mount the plugins. execute the following command: | ||
|
||
```bash | ||
docker run --name c1-trino -d -p 8080:8080 <image-name> -v `gravitino-trino-connector-<version>`:/usr/lib/trino/plugin/gravitino | ||
-v `gravitino-trino-cascading-connector-<version>`:/usr/lib/trino/plugin/trino | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can merge them as
docker run --name {machine_hostname} -d -p 8080:8080 <image-name> -v `gravitino-trino-connector-<version>`:/usr/lib/trino/plugin/gravitino
-v `gravitino-trino-cascading-connector-<version>`:/usr/lib/trino/plugin/trino
|
||
## Deploying Trino | ||
|
||
To set up the Trino cascading query environment, you should first deploy at least two Trino environments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mchades Please also take a look.
...c/main/java/org/apache/gravitino/trino/connector/catalog/DefaultCatalogConnectorFactory.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM.
What changes were proposed in this pull request?
Support the Trino cascading connector
Why are the changes needed?
Fix: #4962
Does this PR introduce any user-facing change?
No
How was this patch tested?
Add some ut and Manually test