This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/polaris.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 0c7b1c88a deploy: 78d572392f6907cb31f3a764baf90137fcad4d14
0c7b1c88a is described below

commit 0c7b1c88a224a922819dcd6470ca2c74367f4647
Author: dimas-b <dima...@users.noreply.github.com>
AuthorDate: Wed Aug 13 20:24:52 2025 +0000

    deploy: 78d572392f6907cb31f3a764baf90137fcad4d14
---
 in-dev/unreleased/metastores/index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/in-dev/unreleased/metastores/index.html 
b/in-dev/unreleased/metastores/index.html
index 60d6378eb..a7e57195c 100644
--- a/in-dev/unreleased/metastores/index.html
+++ b/in-dev/unreleased/metastores/index.html
@@ -42,7 +42,7 @@ QUARKUS_DATASOURCE_PASSWORD=&lt;your-password&gt;
 QUARKUS_DATASOURCE_JDBC_URL=&lt;jdbc-url-of-postgres&gt;
 </code></pre><p>The Relational JDBC metastore currently relies on a 
Quarkus-managed datasource and supports only PostgresSQL and H2 databases. This 
limitation is similar to that of EclipseLink, primarily due to underlying 
schema differences. At this time, official documentation is provided 
exclusively for usage with PostgreSQL.
 Please refer to the documentation here:
-<a href=https://quarkus.io/guides/datasource>Configure data sources in 
Quarkus</a></p><p>Additionally the retries can be configured via 
<code>polaris.persistence.relational.jdbc.*</code> properties please ref <a 
href=./configuration.md>configuration</a></p><h2 
id=eclipselink-deprecated>EclipseLink 
(Deprecated)</h2><blockquote><p>[!IMPORTANT]
+<a href=https://quarkus.io/guides/datasource>Configure data sources in 
Quarkus</a></p><p>Additionally the retries can be configured via 
<code>polaris.persistence.relational.jdbc.*</code> properties please ref <a 
href=https://polaris.apache.org/in-dev/unreleased/configuration/>configuration</a></p><h2
 id=eclipselink-deprecated>EclipseLink 
(Deprecated)</h2><blockquote><p>[!IMPORTANT]
 Eclipse link is deprecated, its recommend to use Relational JDBC as 
persistence instead.</p></blockquote><p>Polaris includes EclipseLink plugin by 
default with PostgresSQL driver.</p><p>Configure the 
<code>polaris.persistence</code> section in your Polaris configuration file
 (<code>application.properties</code>) as follows:</p><pre 
tabindex=0><code>polaris.persistence.type=eclipse-link
 polaris.persistence.eclipselink.configuration-file=/path/to/persistence.xml
@@ -55,7 +55,7 @@ You have to locate the <code>persistence.xml</code> at least 
two folders down to
 [Quarkus Configuration Reference]: <a 
href=https://quarkus.io/guides/config-reference>https://quarkus.io/guides/config-reference</a>
 [EclipseLink configuration file]: <a 
href=https://eclipse.dev/eclipselink/documentation/4.0/solutions/solutions.html#TESTINGJPA002>https://eclipse.dev/eclipselink/documentation/4.0/solutions/solutions.html#TESTINGJPA002</a></p></blockquote><p>Polaris
 creates and connects to a separate database for each realm. Specifically, the 
<code>{realm}</code> placeholder in <code>jakarta.persistence.jdbc.url</code> 
is substituted with the actual realm name, allowing the Polaris server to 
connect to  [...]
 Some database systems such as Postgres don&rsquo;t create databases 
automatically. Database admins need to create them manually before running 
Polaris server.</p></blockquote><p>A single <code>persistence.xml</code> can 
describe multiple <a 
href=https://eclipse.dev/eclipselink/documentation/4.0/concepts/concepts.html#APPDEV001>persistence
 units</a>. For example, with both a <code>polaris-dev</code> and 
<code>polaris</code> persistence unit defined, you could use a single 
<code>persistenc [...]
-H2 is an in-memory database and is not suitable for 
production!</p></blockquote><p>The default <a 
href=https://github.com/apache/polaris/blob/main/extension/persistence/eclipselink/src/main/resources/META-INF/persistence.xml>persistence.xml</a>
 in Polaris is already configured for H2, but you can easily customize
+H2 is an in-memory database and is not suitable for 
production!</p></blockquote><p>The default <a 
href=https://github.com/apache/polaris/blob/main/persistence/eclipselink/src/main/resources/META-INF/persistence.xml>persistence.xml</a>
 in Polaris is already configured for H2, but you can easily customize
 your H2 configuration using the persistence unit template below:</p><div 
class=highlight><pre tabindex=0 
style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
 class=language-xml data-lang=xml><span style=display:flex><span><span 
style=color:#f92672>&lt;persistence-unit</span> <span 
style=color:#a6e22e>name=</span><span 
style=color:#e6db74>&#34;polaris&#34;</span> <span 
style=color:#a6e22e>transaction-type=</span><span 
style=color:#e6db74>&#34;RESOURC [...]
 </span></span><span style=display:flex><span>    <span 
style=color:#f92672>&lt;provider&gt;</span>org.eclipse.persistence.jpa.PersistenceProvider<span
 style=color:#f92672>&lt;/provider&gt;</span>
 </span></span><span style=display:flex><span>    <span 
style=color:#f92672>&lt;class&gt;</span>org.apache.polaris.extension.persistence.impl.eclipselink.models.ModelEntity<span
 style=color:#f92672>&lt;/class&gt;</span>

Reply via email to