-
Notifications
You must be signed in to change notification settings - Fork 227
Doc: Add getting started with JDBC source #1470
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
base: main
Are you sure you want to change the base?
Conversation
eff619c
to
f711cc1
Compare
...n/java/org/apache/polaris/extension/persistence/relational/jdbc/JdbcBasePersistenceImpl.java
Outdated
Show resolved
Hide resolved
f6f8520
to
7d3f4ea
Compare
7d3f4ea
to
712d1bd
Compare
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.
LGTM overall. It's a not blocker, but there'd be some other docs needed to be updated.
- https://polaris.apache.org/in-dev/unreleased/metastores/
- https://polaris.apache.org/in-dev/unreleased/configuring-polaris-for-production/#metastore-configuration, we will suggest JDBC over eclipseLink for production.
- https://polaris.apache.org/in-dev/unreleased/admin-tool/, this is blocked by the PR to reenable boostrap logic for jdbc.
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, looks good. Few comments below, and a few high-level comments:
- We also need to update the existing Quickstart documents to start using Relational JDBC instead of Eclipselink as well. @singhpk234 - did you want to make these changes? Or I can take that up after this merges.
- Have we tested all of these both locally and on at least one cloud provider? If not locally, that should be a blocker. For a cloud provider, it isn't a blocker - but we should take as a fast-follow to verify this.
|
||
This example requires `jq` to be installed on your machine. | ||
|
||
1. If such an image is not already present, build the Polaris image with support for EclipseLink and |
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.
1. If such an image is not already present, build the Polaris image with support for EclipseLink and | |
1. If such an image is not already present, build the Polaris image with support for JDBC persistence and |
``` | ||
docker exec -it jdbc-trino-1 trino | ||
``` | ||
Note, `trino-trino-1` is the name of the Docker container. |
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.
Note, `trino-trino-1` is the name of the Docker container. | |
Note, `jdbc-trino-1` is the name of the Docker container. |
``` | ||
|
||
6. Using Trino CLI: To access the Trino CLI, run this command: | ||
``` |
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.
``` | |
```shell |
# under the License. | ||
# | ||
|
||
services: |
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.
Is it the same postgres container than for EclipseLink? Maybe we can avoid duplicating this?
services: | ||
|
||
polaris: | ||
# IMPORTANT: the image MUST contain the Postgres JDBC driver and EclipseLink dependencies, see README for instructions |
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.
# IMPORTANT: the image MUST contain the Postgres JDBC driver and EclipseLink dependencies, see README for instructions | |
# IMPORTANT: the image MUST contain the Postgres JDBC driver and JDBC persistence, see README for instructions |
About the change