This is an automated email from the ASF dual-hosted git repository.
emaynard pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/polaris.git
The following commit(s) were added to refs/heads/main by this push:
new 5c0433f5 Add extra docs about using EclipseLink (#195)
5c0433f5 is described below
commit 5c0433f5583b5e445b5cc072b29fdeb08865e460
Author: Daniel van der Ende <[email protected]>
AuthorDate: Mon Oct 21 05:00:01 2024 +0200
Add extra docs about using EclipseLink (#195)
* Add extra docs about using EclipseLink
* Process review comments
* Handle more review comments
---------
Co-authored-by: Eric Maynard <[email protected]>
---
.../in-dev/unreleased/configuring-polaris-for-production.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git
a/site/content/in-dev/unreleased/configuring-polaris-for-production.md
b/site/content/in-dev/unreleased/configuring-polaris-for-production.md
index 86ccd195..6b66c2bf 100644
--- a/site/content/in-dev/unreleased/configuring-polaris-for-production.md
+++ b/site/content/in-dev/unreleased/configuring-polaris-for-production.md
@@ -61,6 +61,13 @@ Be sure to secure your metastore backend since it will be
storing credentials an
To use EclipseLink for metastore management, specify the configuration
`metaStoreManager.conf-file` to point to an EclipseLink `persistence.xml` file.
This file, local to the Polaris service, contains details of the database used
for metastore management and the connection settings. For more information,
refer to the [metastore documentation]({{% ref "metastores" %}}).
+> [!IMPORTANT]
+> EclipseLink requires
+> 1. Building the JAR for the EclipseLink extension
+> 2. Setting the `eclipseLink` gradle property to `true`.
+>
+> This can be achieved by setting `eclipseLink=true` in the
`gradle.properties` file, or by passing the property explicitly while building
all JARs, e.g.: `./gradlew -PeclipseLink=true clean assemble`
+
### Bootstrapping
Before using Polaris when using a metastore manager other than `in-memory`,
you must **bootstrap** the metastore manager. This is a manual operation that
must be performed **only once** in order to prepare the metastore manager to
integrate with Polaris. When the metastore manager is bootstrapped, any
existing Polaris entities in the metastore manager may be **purged**.
