Quickstart getting-started/jdbc launches polaris connected to h2 storage

[pjanuario]

Describe the bug

As JDBC is being advertised as the prefered production deployment configuration and eclipse link is getting deprecated I was unable to follow the quickstart to launch a running instance connected to postgres following https://github.com/apache/polaris/tree/main/getting-started/jdbc#getting-started-with-apache-polaris-relational-jdbc-postgres-and-spark-sql

To Reproduce

Follow the steps mentioned in quickstart

Actual Behavior

polaris-1  | 2025-05-27 16:43:59,789 WARN  [org.apa.pol.ser.qua.con.ProductionReadinessChecks] [,] [,,,] (main) - ⚠️ The current persistence unit (jdbc:h2) is intended for tests only. Offending configuration option: 'polaris.persistence.eclipselink.configuration-file'.

Expected Behavior

Expected to be connected to postgres instance instead of h2.

Additional context

No response

System information

No response

[singhpk234]

Eclipselink should not be running at all, this is production readiness check i think it doesn't takes into consideration the persistence being used. I think that need to be fixed.

Though why would you say that you are unable to run it are you unable to see the logs in the postgres container ?
seems like some more changes went in to the quick start recently

[flyrain]

Hi @pjanuario, can you check if the Polaris connected to your postgres instance? If yes, we need to fix the misleading message.

[pjanuario]

I will deep dive a bit, before previous changes to the quickstart I looked at it and the database had no objects being created, with this changes I didn't doubled checked yet.
I will check how to enable de ug logging and if there is any helpful logging and if objects are being created.

[pjanuario]

I have checked this and indeed it seems just the rediness checks.

root@d869fffbdb91:/# psql -d POLARIS -U postgres
psql (17.5 (Debian 17.5-1.pgdg120+1))
Type "help" for help.

POLARIS=# \l
                                                    List of databases
   Name    |  Owner   | Encoding | Locale Provider |  Collate   |   Ctype    | Locale | ICU Rules |   Access privileges
-----------+----------+----------+-----------------+------------+------------+--------+-----------+-----------------------
 POLARIS   | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |        |           |
 postgres  | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |        |           |
 template0 | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |        |           | =c/postgres          +
           |          |          |                 |            |            |        |           | postgres=CTc/postgres
 template1 | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |        |           | =c/postgres          +
           |          |          |                 |            |            |        |           | postgres=CTc/postgres
(4 rows)

POLARIS=# \dn
          List of schemas
      Name      |       Owner
----------------+-------------------
 polaris_schema | postgres
 public         | pg_database_owner
(2 rows)

POLARIS=# \dt polaris_schema
Did not find any relation named "polaris_schema".
POLARIS=# \dt polaris_schema.*
                         List of relations
     Schema     |             Name              | Type  |  Owner
----------------+-------------------------------+-------+----------
 polaris_schema | entities                      | table | postgres
 polaris_schema | grant_records                 | table | postgres
 polaris_schema | policy_mapping_record         | table | postgres
 polaris_schema | principal_authentication_data | table | postgres
(4 rows)

While diving I noticed that polaris uses the schema polaris_schema, this might be interesting to document or adjust the examples to provide an explicit schema. This way it would be easier to understand the defaults.

[flyrain]

Thanks @pjanuario for the confirmation! #1707 will fix it.

[singhpk234]

closing this ticket as the above PR is merged, Thanks @flyrain for the review !

Thanks @pjanuario for reporting !