Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

singhpk234
Copy link
Collaborator

@singhpk234 singhpk234 commented Apr 27, 2025

About the change

  • Add the getting started doc for using Polaris with the new JDBC persistence layer
  • Fixes a bug in purge

@singhpk234 singhpk234 force-pushed the feature/getting-started-jdbc branch from eff619c to f711cc1 Compare April 27, 2025 07:12
@singhpk234 singhpk234 force-pushed the feature/getting-started-jdbc branch from f6f8520 to 7d3f4ea Compare April 28, 2025 19:38
@singhpk234 singhpk234 force-pushed the feature/getting-started-jdbc branch from 7d3f4ea to 712d1bd Compare April 28, 2025 19:53
Copy link
Contributor

@flyrain flyrain left a 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.

  1. https://polaris.apache.org/in-dev/unreleased/metastores/
  2. https://polaris.apache.org/in-dev/unreleased/configuring-polaris-for-production/#metastore-configuration, we will suggest JDBC over eclipseLink for production.
  3. https://polaris.apache.org/in-dev/unreleased/admin-tool/, this is blocked by the PR to reenable boostrap logic for jdbc.

Copy link
Collaborator

@adnanhemani adnanhemani left a 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:

  1. 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.
  2. 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
```
```shell

# under the License.
#

services:
Copy link
Contributor

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants