-
Notifications
You must be signed in to change notification settings - Fork 496
Update metastores.md #1537
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
Merged
Merged
Update metastores.md #1537
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -22,17 +22,10 @@ type: docs | |
| weight: 700 | ||
| --- | ||
|
|
||
| This page documents important configurations for connecting to a production database through [EclipseLink](https://eclipse.dev/eclipselink/). | ||
| This page explains how to configure and use Polaris metastores with either the recommended Relational JDBC or the | ||
| deprecated EclipseLink persistence backends. | ||
|
|
||
| ## Polaris EclipseLink | ||
|
|
||
| Polaris includes EclipseLink plugin by default with PostgreSQL driver. | ||
|
|
||
| In order to add other JDBC drivers, you have to build Polaris using the `eclipseLinkDeps` build property. | ||
|
|
||
| ## Polaris Server Configuration | ||
|
|
||
| ### Relational JDBC | ||
| ## Relational JDBC | ||
| This implementation leverages Quarkus for datasource management and supports configuration through | ||
| environment variables or JVM -D flags at startup. For more information, refer to the [Quarkus configuration reference](https://quarkus.io/guides/config-reference#env-file). | ||
|
|
||
|
|
@@ -50,7 +43,7 @@ The Relational JDBC metastore currently relies on a Quarkus-managed datasource a | |
| Please refer to the documentation here: | ||
| [Configure data sources in Quarkus](https://quarkus.io/guides/datasource) | ||
|
|
||
| ### EclipseLink | ||
| ## EclipseLink(Deprecated) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: add space before
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixed |
||
| > [!IMPORTANT] Eclipse link is deprecated, its recommend to use Relational JDBC as persistence instead. | ||
|
|
||
| Configure the `polaris.persistence` section in your Polaris configuration file | ||
|
|
@@ -79,7 +72,7 @@ Polaris creates and connects to a separate database for each realm. Specifically | |
|
|
||
| A single `persistence.xml` can describe multiple [persistence units](https://eclipse.dev/eclipselink/documentation/4.0/concepts/concepts.html#APPDEV001). For example, with both a `polaris-dev` and `polaris` persistence unit defined, you could use a single `persistence.xml` to easily switch between development and production databases. Use the `persistence-unit` option in the Polaris server configuration to easily switch between persistence units. | ||
|
|
||
| #### Using H2 | ||
| ### Using H2 | ||
|
|
||
| > [!IMPORTANT] H2 is an in-memory database and is not suitable for production! | ||
|
|
||
|
|
@@ -122,7 +115,7 @@ java -Dpolaris.persistence.type=eclipse-link \ | |
| -jar quarkus/server/build/quarkus-app/quarkus-run.jar | ||
| ``` | ||
|
|
||
| #### Using Postgres | ||
| ### Using Postgres | ||
|
|
||
| PostgreSQL is included by default in the Polaris server distribution. | ||
|
|
||
|
|
||
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.
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.
This info is lost now, should we copy this to the eclipse link i.e the plugin and postgres driver is packaged with eclipse-link ?
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.
Fixed in the new commit.