pingtimeout commented on code in PR #1515:
URL: https://github.com/apache/polaris/pull/1515#discussion_r2072604155


##########
site/content/in-dev/unreleased/metastores.md:
##########
@@ -32,6 +32,29 @@ In order to add other JDBC drivers, you have to build 
Polaris using the `eclipse
 
 ## Polaris Server Configuration
 
+#### Relational JDBC

Review Comment:
   It seems to me that this section should be at level 3 to match the 
EclipseLink section below.
   
   ```suggestion
   ### Relational JDBC
   ```



##########
site/content/in-dev/unreleased/metastores.md:
##########
@@ -32,6 +32,29 @@ In order to add other JDBC drivers, you have to build 
Polaris using the `eclipse
 
 ## Polaris Server Configuration
 
+#### Relational JDBC
+Configure the `polaris.persistence` section in your Polaris configuration file
+(`application.properties`) as follows:
+
+```
+polaris.persistence.type=relational-jdbc
+
+quarkus.datasource.db-kind=postgresql
+quarkus.datasource.username=<your username>
+quarkus.datasource.password=<your password>
+
+quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/<database_name>
+```
+
+The relational JDBC metastore is a Quarkus-managed datasource and only 
supports Postgres and H2 as of now.
+Please refer to the documentation here:
+[Configure data sources in Quarkus](https://quarkus.io/guides/datasource)
+
+Note: Polaris will always create schema 'polaris_schema' during bootstrap 
under the configured database.
+

Review Comment:
   Nit: we say that the relational JDBC persistence supports Postgres and H2 
(just like EclipseLink), but we only document how to use it with Postgres.  
That could suggest that either H2 is not usable with that persistence 
implementation or could mislead people into using EclipseLink.  Should there be 
a `#### Using Postgres` and a `#### Using H2` subsection?



##########
quarkus/admin/src/testFixtures/java/org/apache/polaris/admintool/PostgresTestResourceLifecycleManager.java:
##########
@@ -63,7 +63,10 @@ public Map<String, String> start() {
     context.containerNetworkId().ifPresent(postgres::withNetworkMode);
     postgres.start();
     return Map.of(
-        "polaris.persistence.eclipselink.configuration-file", 
createPersistenceXml().toString());
+        "polaris.persistence.type",
+        "eclipse-link",

Review Comment:
   Is this because all tests currently run against the EclipseLink 
implementation?



##########
site/content/in-dev/unreleased/configuring-polaris-for-production.md:
##########
@@ -135,33 +135,26 @@ default, Polaris uses an in-memory metastore.
 > The default in-memory metastore is not suitable for production use, as it 
 > will lose all data
 > when the server is restarted; it is also unusable when multiple Polaris 
 > replicas are used.
 
-To use a durable metastore, you need to switch to the EclipseLink metastore, 
and provide your own
-`persistence.xml` file. This file contains details of the database used for 
metastore management and
-the connection settings. For more information, refer to the [metastore 
documentation]({{% ref
-"metastores" %}}).
+To use a durable metastore, you need to switch to the Relational JDBC backed 
metastore 

Review Comment:
   ```suggestion
   To use a durable metastore, you need to switch to the Relational JDBC backed 
metastore.
   ```



##########
site/content/in-dev/unreleased/configuring-polaris-for-production.md:
##########
@@ -135,33 +135,26 @@ default, Polaris uses an in-memory metastore.
 > The default in-memory metastore is not suitable for production use, as it 
 > will lose all data
 > when the server is restarted; it is also unusable when multiple Polaris 
 > replicas are used.
 
-To use a durable metastore, you need to switch to the EclipseLink metastore, 
and provide your own
-`persistence.xml` file. This file contains details of the database used for 
metastore management and
-the connection settings. For more information, refer to the [metastore 
documentation]({{% ref
-"metastores" %}}).
+To use a durable metastore, you need to switch to the Relational JDBC backed 
metastore 
 
-Then, configure Polaris to use your metastore by setting the following 
properties:
+Configure the `polaris.persistence` section in your Polaris configuration file
+(`application.properties`) as follows:
 
-```properties
-polaris.persistence.type=eclipse-link
-polaris.persistence.eclipselink.configuration-file=/path/to/persistence.xml
-polaris.persistence.eclipselink.persistence-unit=polaris
 ```
+polaris.persistence.type=relational-jdbc
 
-Where:
+quarkus.datasource.db-kind=postgresql
+quarkus.datasource.username=<your username>
+quarkus.datasource.password=<your password>
 
-- `polaris.persistence.type` indicates that we are using the EclipseLink 
metastore.
-- `polaris.persistence.eclipselink.configuration-file` is the path to the 
`persistence.xml` file.
-- `polaris.persistence.eclipselink.persistence-unit` is the name of the 
persistence unit to use (in
-  case the configuration file has many persistence units).
+quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/<database_name>
+```
 
-Typically, in Kubernetes, you would define the `persistence.xml` file as a 
`ConfigMap` and set the
-`polaris.persistence.eclipselink.configuration-file` property to the path of 
the mounted file in
-the container.
+The relational JDBC metastore is a Quarkus-managed datasource and only 
supports Postgres and H2 as of now.
+Please refer to the documentation here:
+[Configure data sources in Quarkus](https://quarkus.io/guides/datasource)
 
-> [!IMPORTANT]
-> Be sure to secure your metastore backend since it will be storing sensitive 
data and catalog
-> metadata.

Review Comment:
   The fact that this warning is removed suggests that no sensitive data is 
stored in the metastore anymore.  Is it the case?



##########
helm/polaris/README.md:
##########
@@ -186,161 +186,161 @@ kubectl delete namespace polaris
 
 ## Values
 
-| Key | Type | Default | Description |
-|-----|------|---------|-------------|
-| advancedConfig | object | `{}` | Advanced configuration. You can pass here 
any valid Polaris or Quarkus configuration property. Any property that is 
defined here takes precedence over all the other configuration values generated 
by this chart. Properties can be passed "flattened" or as nested YAML objects 
(see examples below). Note: values should be strings; avoid using numbers, 
booleans, or other types. |
-| affinity | object | `{}` | Affinity and anti-affinity for polaris pods. See 
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity.
 |
-| authentication | object | 
`{"authenticator":{"type":"default"},"tokenBroker":{"maxTokenGeneration":"PT1H","secret":{"name":null,"privateKey":"private.pem","publicKey":"public.pem","secretKey":"secret"},"type":"rsa-key-pair"},"tokenService":{"type":"default"}}`
 | Polaris authentication configuration. |
-| authentication.authenticator | object | `{"type":"default"}` | The type of 
authentication to use. Two built-in types are supported: default and test; test 
is not recommended for production. |
-| authentication.tokenBroker | object | 
`{"maxTokenGeneration":"PT1H","secret":{"name":null,"privateKey":"private.pem","publicKey":"public.pem","secretKey":"secret"},"type":"rsa-key-pair"}`
 | The type of token broker to use. Two built-in types are supported: 
rsa-key-pair and symmetric-key. |
-| authentication.tokenBroker.secret | object | 
`{"name":null,"privateKey":"private.pem","publicKey":"public.pem","secretKey":"secret"}`
 | The secret name to pull the public and private keys, or the symmetric key 
secret from. |
-| authentication.tokenBroker.secret.name | string | `nil` | The name of the 
secret to pull the keys from. If not provided, a key pair will be generated. 
This is not recommended for production. |
-| authentication.tokenBroker.secret.privateKey | string | `"private.pem"` | 
The private key file to use for RSA key pair token broker. Only required when 
using rsa-key-pair. |
-| authentication.tokenBroker.secret.publicKey | string | `"public.pem"` | The 
public key file to use for RSA key pair token broker. Only required when using 
rsa-key-pair. |
-| authentication.tokenBroker.secret.secretKey | string | `"secret"` | The 
symmetric key file to use for symmetric key token broker. Only required when 
using symmetric-key. |
-| authentication.tokenService | object | `{"type":"default"}` | The type of 
token service to use. Two built-in types are supported: default and test; test 
is not recommended for production. |
-| autoscaling.enabled | bool | `false` | Specifies whether automatic 
horizontal scaling should be enabled. Do not enable this when using in-memory 
version store type. |
-| autoscaling.maxReplicas | int | `3` | The maximum number of replicas to 
maintain. |
-| autoscaling.minReplicas | int | `1` | The minimum number of replicas to 
maintain. |
-| autoscaling.targetCPUUtilizationPercentage | int | `80` | Optional; set to 
zero or empty to disable. |
-| autoscaling.targetMemoryUtilizationPercentage | string | `nil` | Optional; 
set to zero or empty to disable. |
-| configMapLabels | object | `{}` | Additional Labels to apply to polaris 
configmap. |
-| containerSecurityContext | object | 
`{"allowPrivilegeEscalation":false,"capabilities":{"drop":["ALL"]},"runAsNonRoot":true,"runAsUser":10000,"seccompProfile":{"type":"RuntimeDefault"}}`
 | Security context for the polaris container. See 
https://kubernetes.io/docs/tasks/configure-pod-container/security-context/. |
-| containerSecurityContext.runAsUser | int | `10000` | UID 10000 is compatible 
with Polaris OSS default images; change this if you are using a different 
image. |
-| cors | object | 
`{"accessControlAllowCredentials":null,"accessControlMaxAge":null,"allowedHeaders":[],"allowedMethods":[],"allowedOrigins":[],"exposedHeaders":[]}`
 | Polaris CORS configuration. |
-| cors.accessControlAllowCredentials | string | `nil` | The 
`Access-Control-Allow-Credentials` response header. The value of this header 
will default to `true` if `allowedOrigins` property is set and there is a match 
with the precise `Origin` header. |
-| cors.accessControlMaxAge | string | `nil` | The `Access-Control-Max-Age` 
response header value indicating how long the results of a pre-flight request 
can be cached. Must be a valid duration. |
-| cors.allowedHeaders | list | `[]` | HTTP headers allowed for CORS, ex: 
X-Custom, Content-Disposition. If this is not set or empty, all requested 
headers are considered allowed. |
-| cors.allowedMethods | list | `[]` | HTTP methods allowed for CORS, ex: GET, 
PUT, POST. If this is not set or empty, all requested methods are considered 
allowed. |
-| cors.allowedOrigins | list | `[]` | Origins allowed for CORS, e.g. 
http://polaris.apache.org, http://localhost:8181. In case an entry of the list 
is surrounded by forward slashes, it is interpreted as a regular expression. |
-| cors.exposedHeaders | list | `[]` | HTTP headers exposed to the client, ex: 
X-Custom, Content-Disposition. The default is an empty list. |
-| extraEnv | list | `[]` | Advanced configuration via Environment Variables. 
Extra environment variables to add to the Polaris server container. You can 
pass here any valid EnvVar object: 
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#envvar-v1-core
 This can be useful to get configuration values from Kubernetes secrets or 
config maps. |
-| extraInitContainers | list | `[]` | Add additional init containers to the 
polaris pod(s) See 
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/. |
-| extraServices | list | `[]` | Additional service definitions. All service 
definitions always select all Polaris pods. Use this if you need to expose 
specific ports with different configurations, e.g. expose polaris-http with an 
alternate LoadBalancer service instead of ClusterIP. |
-| extraVolumeMounts | list | `[]` | Extra volume mounts to add to the polaris 
container. See https://kubernetes.io/docs/concepts/storage/volumes/. |
-| extraVolumes | list | `[]` | Extra volumes to add to the polaris pod. See 
https://kubernetes.io/docs/concepts/storage/volumes/. |
-| features | object | `{"defaults":{},"realmOverrides":{}}` | Polaris features 
configuration. |
-| features.defaults | object | `{}` | Features to enable or disable globally. 
If a feature is not present in the map, the default built-in value is used. |
-| features.realmOverrides | object | `{}` | Features to enable or disable per 
realm. This field is a map of maps. The realm name is the key, and the value is 
a map of feature names to values. If a feature is not present in the map, the 
default value from the 'defaults' field is used. |
-| fileIo | object | `{"type":"default"}` | Polaris FileIO configuration. |
-| fileIo.type | string | `"default"` | The type of file IO to use. Two 
built-in types are supported: default and wasb. The wasb one translates WASB 
paths to ABFS ones. |
-| image.configDir | string | `"/deployments/config"` | The path to the 
directory where the application.properties file, and other configuration files, 
if any, should be mounted. Note: if you are using EclipseLink, then this value 
must be at least two folders down to the root folder, e.g. 
`/deployments/config` is OK, whereas `/deployments` is not. |
-| image.pullPolicy | string | `"IfNotPresent"` | The image pull policy. |
-| image.repository | string | `"apache/polaris"` | The image repository to 
pull from. |
-| image.tag | string | `"latest"` | The image tag. |
-| imagePullSecrets | list | `[]` | References to secrets in the same namespace 
to use for pulling any of the images used by this chart. Each entry is a 
LocalObjectReference to an existing secret in the namespace. The secret must 
contain a .dockerconfigjson key with a base64-encoded Docker configuration 
file. See 
https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
 for more information. |
-| ingress.annotations | object | `{}` | Annotations to add to the ingress. |
-| ingress.className | string | `""` | Specifies the ingressClassName; leave 
empty if you don't want to customize it |
-| ingress.enabled | bool | `false` | Specifies whether an ingress should be 
created. |
-| ingress.hosts | list | `[{"host":"chart-example.local","paths":[]}]` | A 
list of host paths used to configure the ingress. |
-| ingress.tls | list | `[]` | A list of TLS certificates; each entry has a 
list of hosts in the certificate, along with the secret name used to terminate 
TLS traffic on port 443. |
-| livenessProbe | object | 
`{"failureThreshold":3,"initialDelaySeconds":5,"periodSeconds":10,"successThreshold":1,"terminationGracePeriodSeconds":30,"timeoutSeconds":10}`
 | Configures the liveness probe for polaris pods. |
-| livenessProbe.failureThreshold | int | `3` | Minimum consecutive failures 
for the probe to be considered failed after having succeeded. Minimum value is 
1. |
-| livenessProbe.initialDelaySeconds | int | `5` | Number of seconds after the 
container has started before liveness probes are initiated. Minimum value is 0. 
|
-| livenessProbe.periodSeconds | int | `10` | How often (in seconds) to perform 
the probe. Minimum value is 1. |
-| livenessProbe.successThreshold | int | `1` | Minimum consecutive successes 
for the probe to be considered successful after having failed. Minimum value is 
1. |
-| livenessProbe.terminationGracePeriodSeconds | int | `30` | Optional duration 
in seconds the pod needs to terminate gracefully upon probe failure. Minimum 
value is 1. |
-| livenessProbe.timeoutSeconds | int | `10` | Number of seconds after which 
the probe times out. Minimum value is 1. |
-| logging | object | 
`{"categories":{"org.apache.iceberg.rest":"INFO","org.apache.polaris":"INFO"},"console":{"enabled":true,"format":"%d{yyyy-MM-dd
 HH:mm:ss,SSS} %-5p [%c{3.}] [%X{requestId},%X{realmId}] 
[%X{traceId},%X{parentId},%X{spanId},%X{sampled}] (%t) 
%s%e%n","json":false,"threshold":"ALL"},"file":{"enabled":false,"fileName":"polaris.log","format":"%d{yyyy-MM-dd
 HH:mm:ss,SSS} %-5p [%c{3.}] [%X{requestId},%X{realmId}] 
[%X{traceId},%X{parentId},%X{spanId},%X{sampled}] (%t) 
%s%e%n","json":false,"logsDir":"/deployments/logs","rotation":{"fileSuffix":null,"maxBackupIndex":5,"maxFileSize":"100Mi"},"storage":{"className":"standard","selectorLabels":{},"size":"512Gi"},"threshold":"ALL"},"level":"INFO","mdc":{},"requestIdHeaderName":"Polaris-Request-Id"}`
 | Logging configuration. |
-| logging.categories | object | 
`{"org.apache.iceberg.rest":"INFO","org.apache.polaris":"INFO"}` | 
Configuration for specific log categories. |
-| logging.console | object | `{"enabled":true,"format":"%d{yyyy-MM-dd 
HH:mm:ss,SSS} %-5p [%c{3.}] [%X{requestId},%X{realmId}] 
[%X{traceId},%X{parentId},%X{spanId},%X{sampled}] (%t) 
%s%e%n","json":false,"threshold":"ALL"}` | Configuration for the console 
appender. |
-| logging.console.enabled | bool | `true` | Whether to enable the console 
appender. |
-| logging.console.format | string | `"%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p 
[%c{3.}] [%X{requestId},%X{realmId}] 
[%X{traceId},%X{parentId},%X{spanId},%X{sampled}] (%t) %s%e%n"` | The log 
format to use. Ignored if JSON format is enabled. See 
https://quarkus.io/guides/logging#logging-format for details. |
-| logging.console.json | bool | `false` | Whether to log in JSON format. |
-| logging.console.threshold | string | `"ALL"` | The log level of the console 
appender. |
-| logging.file | object | 
`{"enabled":false,"fileName":"polaris.log","format":"%d{yyyy-MM-dd 
HH:mm:ss,SSS} %-5p [%c{3.}] [%X{requestId},%X{realmId}] 
[%X{traceId},%X{parentId},%X{spanId},%X{sampled}] (%t) 
%s%e%n","json":false,"logsDir":"/deployments/logs","rotation":{"fileSuffix":null,"maxBackupIndex":5,"maxFileSize":"100Mi"},"storage":{"className":"standard","selectorLabels":{},"size":"512Gi"},"threshold":"ALL"}`
 | Configuration for the file appender. |
-| logging.file.enabled | bool | `false` | Whether to enable the file appender. 
|
-| logging.file.fileName | string | `"polaris.log"` | The log file name. |
-| logging.file.format | string | `"%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c{3.}] 
[%X{requestId},%X{realmId}] [%X{traceId},%X{parentId},%X{spanId},%X{sampled}] 
(%t) %s%e%n"` | The log format to use. Ignored if JSON format is enabled. See 
https://quarkus.io/guides/logging#logging-format for details. |
-| logging.file.json | bool | `false` | Whether to log in JSON format. |
-| logging.file.logsDir | string | `"/deployments/logs"` | The local directory 
where log files are stored. The persistent volume claim will be mounted here. |
-| logging.file.rotation | object | 
`{"fileSuffix":null,"maxBackupIndex":5,"maxFileSize":"100Mi"}` | Log rotation 
configuration. |
-| logging.file.rotation.fileSuffix | string | `nil` | An optional suffix to 
append to the rotated log files. If present, the rotated log files will be 
grouped in time buckets, and each bucket will contain at most maxBackupIndex 
files. The suffix must be in a date-time format that is understood by 
DateTimeFormatter. If the suffix ends with .gz or .zip, the rotated files will 
also be compressed using the corresponding algorithm. |
-| logging.file.rotation.maxBackupIndex | int | `5` | The maximum number of 
backup files to keep. |
-| logging.file.rotation.maxFileSize | string | `"100Mi"` | The maximum size of 
the log file before it is rotated. Should be expressed as a Kubernetes 
quantity. |
-| logging.file.storage | object | 
`{"className":"standard","selectorLabels":{},"size":"512Gi"}` | The log storage 
configuration. A persistent volume claim will be created using these settings. |
-| logging.file.storage.className | string | `"standard"` | The storage class 
name of the persistent volume claim to create. |
-| logging.file.storage.selectorLabels | object | `{}` | Labels to add to the 
persistent volume claim spec selector; a persistent volume with matching labels 
must exist. Leave empty if using dynamic provisioning. |
-| logging.file.storage.size | string | `"512Gi"` | The size of the persistent 
volume claim to create. |
-| logging.file.threshold | string | `"ALL"` | The log level of the file 
appender. |
-| logging.level | string | `"INFO"` | The log level of the root category, 
which is used as the default log level for all categories. |
-| logging.mdc | object | `{}` | Configuration for MDC (Mapped Diagnostic 
Context). Values specified here will be added to the log context of all 
incoming requests and can be used in log patterns. |
-| logging.requestIdHeaderName | string | `"Polaris-Request-Id"` | The header 
name to use for the request ID. |
-| managementService | object | 
`{"annotations":{},"clusterIP":"None","externalTrafficPolicy":null,"internalTrafficPolicy":null,"ports":[{"name":"polaris-mgmt","nodePort":null,"port":8182,"protocol":null,"targetPort":null}],"sessionAffinity":null,"trafficDistribution":null,"type":"ClusterIP"}`
 | Management service settings. These settings are used to configure liveness 
and readiness probes, and to configure the dedicated headless service that will 
expose health checks and metrics, e.g. for metrics scraping and service 
monitoring. |
-| managementService.annotations | object | `{}` | Annotations to add to the 
service. |
-| managementService.clusterIP | string | `"None"` | By default, the management 
service is headless, i.e. it does not have a cluster IP. This is generally the 
right option for exposing health checks and metrics, e.g. for metrics scraping 
and service monitoring. |
-| managementService.ports | list | 
`[{"name":"polaris-mgmt","nodePort":null,"port":8182,"protocol":null,"targetPort":null}]`
 | The ports the management service will listen on. At least one port is 
required; the first port implicitly becomes the HTTP port that the application 
will use for serving management requests. By default, it's 8182. Note: port 
names must be unique and no more than 15 characters long. |
-| managementService.ports[0] | object | 
`{"name":"polaris-mgmt","nodePort":null,"port":8182,"protocol":null,"targetPort":null}`
 | The name of the management port. Required. |
-| managementService.ports[0].nodePort | string | `nil` | The port on each node 
on which this service is exposed when type is NodePort or LoadBalancer. Usually 
assigned by the system. If not specified, a port will be allocated if this 
Service requires one. If this field is specified when creating a Service which 
does not need it, creation will fail. |
-| managementService.ports[0].port | int | `8182` | The port the management 
service listens on. By default, the management interface is exposed on HTTP 
port 8182. |
-| managementService.ports[0].protocol | string | `nil` | The IP protocol for 
this port. Supports "TCP", "UDP", and "SCTP". Default is TCP. |
-| managementService.ports[0].targetPort | string | `nil` | Number or name of 
the port to access on the pods targeted by the service. If this is a string, it 
will be looked up as a named port in the target Pod's container ports. If this 
is not specified, the value of the 'port' field is used. |
-| managementService.type | string | `"ClusterIP"` | The type of service to 
create. Valid values are: ExternalName, ClusterIP, NodePort, and LoadBalancer. 
The default value is ClusterIP. |
-| metrics.enabled | bool | `true` | Specifies whether metrics for the polaris 
server should be enabled. |
-| metrics.tags | object | `{}` | Additional tags (dimensional labels) to add 
to the metrics. |
-| nodeSelector | object | `{}` | Node labels which must match for the polaris 
pod to be scheduled on that node. See 
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector.
 |
-| persistence | object | 
`{"eclipseLink":{"persistenceUnit":"polaris","secret":{"key":"persistence.xml","name":null}},"type":"eclipse-link"}`
 | Polaris persistence configuration. |
-| persistence.eclipseLink | object | 
`{"persistenceUnit":"polaris","secret":{"key":"persistence.xml","name":null}}` 
| The configuration for the eclipse-link persistence manager. |
-| persistence.eclipseLink.persistenceUnit | string | `"polaris"` | The 
persistence unit name to use. |
-| persistence.eclipseLink.secret | object | 
`{"key":"persistence.xml","name":null}` | The secret name to pull 
persistence.xml from. |
-| persistence.eclipseLink.secret.key | string | `"persistence.xml"` | The key 
in the secret to pull persistence.xml from. |
-| persistence.eclipseLink.secret.name | string | `nil` | The name of the 
secret to pull persistence.xml from. If not provided, the default built-in 
persistence.xml will be used. This is probably not what you want. |
-| persistence.type | string | `"eclipse-link"` | The type of persistence to 
use. Two built-in types are supported: in-memory and eclipse-link. |
-| podAnnotations | object | `{}` | Annotations to apply to polaris pods. |
-| podLabels | object | `{}` | Additional Labels to apply to polaris pods. |
-| podSecurityContext | object | 
`{"fsGroup":10001,"seccompProfile":{"type":"RuntimeDefault"}}` | Security 
context for the polaris pod. See 
https://kubernetes.io/docs/tasks/configure-pod-container/security-context/. |
-| podSecurityContext.fsGroup | int | `10001` | GID 10001 is compatible with 
Polaris OSS default images; change this if you are using a different image. |
-| rateLimiter | object | 
`{"tokenBucket":{"requestsPerSecond":9999,"type":"default","window":"PT10S"},"type":"no-op"}`
 | Polaris rate limiter configuration. |
-| rateLimiter.tokenBucket | object | 
`{"requestsPerSecond":9999,"type":"default","window":"PT10S"}` | The 
configuration for the default rate limiter, which uses the token bucket 
algorithm with one bucket per realm. |
-| rateLimiter.tokenBucket.requestsPerSecond | int | `9999` | The maximum 
number of requests per second allowed for each realm. |
-| rateLimiter.tokenBucket.type | string | `"default"` | The type of the token 
bucket rate limiter. Only the default type is supported out of the box. |
-| rateLimiter.tokenBucket.window | string | `"PT10S"` | The time window. |
-| rateLimiter.type | string | `"no-op"` | The type of rate limiter filter to 
use. Two built-in types are supported: default and no-op. |
-| readinessProbe | object | 
`{"failureThreshold":3,"initialDelaySeconds":5,"periodSeconds":10,"successThreshold":1,"timeoutSeconds":10}`
 | Configures the readiness probe for polaris pods. |
-| readinessProbe.failureThreshold | int | `3` | Minimum consecutive failures 
for the probe to be considered failed after having succeeded. Minimum value is 
1. |
-| readinessProbe.initialDelaySeconds | int | `5` | Number of seconds after the 
container has started before readiness probes are initiated. Minimum value is 
0. |
-| readinessProbe.periodSeconds | int | `10` | How often (in seconds) to 
perform the probe. Minimum value is 1. |
-| readinessProbe.successThreshold | int | `1` | Minimum consecutive successes 
for the probe to be considered successful after having failed. Minimum value is 
1. |
-| readinessProbe.timeoutSeconds | int | `10` | Number of seconds after which 
the probe times out. Minimum value is 1. |
-| realmContext | object | `{"realms":["POLARIS"],"type":"default"}` | Realm 
context resolver configuration. |
-| realmContext.realms | list | `["POLARIS"]` | List of valid realms, for use 
with the default realm context resolver. The first realm in the list is the 
default realm. Realms not in this list will be rejected. |
-| realmContext.type | string | `"default"` | The type of realm context 
resolver to use. Two built-in types are supported: default and test; test is 
not recommended for production as it does not perform any realm validation. |
-| replicaCount | int | `1` | The number of replicas to deploy (horizontal 
scaling). Beware that replicas are stateless; don't set this number > 1 when 
using in-memory meta store manager. |
-| resources | object | `{}` | Configures the resources requests and limits for 
polaris pods. We usually recommend not to specify default resources and to 
leave this as a conscious choice for the user. This also increases chances 
charts run on environments with little resources, such as Minikube. If you do 
want to specify resources, uncomment the following lines, adjust them as 
necessary, and remove the curly braces after 'resources:'. |
-| revisionHistoryLimit | string | `nil` | The number of old ReplicaSets to 
retain to allow rollback (if not set, the default Kubernetes value is set to 
10). |
-| service | object | 
`{"annotations":{},"clusterIP":null,"externalTrafficPolicy":null,"internalTrafficPolicy":null,"ports":[{"name":"polaris-http","nodePort":null,"port":8181,"protocol":null,"targetPort":null}],"sessionAffinity":null,"trafficDistribution":null,"type":"ClusterIP"}`
 | Polaris main service settings. |
-| service.annotations | object | `{}` | Annotations to add to the service. |
-| service.clusterIP | string | `nil` | You can specify your own cluster IP 
address If you define a Service that has the .spec.clusterIP set to "None" then 
Kubernetes does not assign an IP address. Instead, DNS records for the service 
will return the IP addresses of each pod targeted by the server. This is called 
a headless service. See 
https://kubernetes.io/docs/concepts/services-networking/service/#headless-services
 |
-| service.externalTrafficPolicy | string | `nil` | Controls how traffic from 
external sources is routed. Valid values are Cluster and Local. The default 
value is Cluster. Set the field to Cluster to route traffic to all ready 
endpoints. Set the field to Local to only route to ready node-local endpoints. 
If the traffic policy is Local and there are no node-local endpoints, traffic 
is dropped by kube-proxy. |
-| service.internalTrafficPolicy | string | `nil` | Controls how traffic from 
internal sources is routed. Valid values are Cluster and Local. The default 
value is Cluster. Set the field to Cluster to route traffic to all ready 
endpoints. Set the field to Local to only route to ready node-local endpoints. 
If the traffic policy is Local and there are no node-local endpoints, traffic 
is dropped by kube-proxy. |
-| service.ports | list | 
`[{"name":"polaris-http","nodePort":null,"port":8181,"protocol":null,"targetPort":null}]`
 | The ports the service will listen on. At least one port is required; the 
first port implicitly becomes the HTTP port that the application will use for 
serving API requests. By default, it's 8181. Note: port names must be unique 
and no more than 15 characters long. |
-| service.ports[0] | object | 
`{"name":"polaris-http","nodePort":null,"port":8181,"protocol":null,"targetPort":null}`
 | The name of the port. Required. |
-| service.ports[0].nodePort | string | `nil` | The port on each node on which 
this service is exposed when type is NodePort or LoadBalancer. Usually assigned 
by the system. If not specified, a port will be allocated if this Service 
requires one. If this field is specified when creating a Service which does not 
need it, creation will fail. |
-| service.ports[0].port | int | `8181` | The port the service listens on. By 
default, the HTTP port is 8181. |
-| service.ports[0].protocol | string | `nil` | The IP protocol for this port. 
Supports "TCP", "UDP", and "SCTP". Default is TCP. |
-| service.ports[0].targetPort | string | `nil` | Number or name of the port to 
access on the pods targeted by the service. If this is a string, it will be 
looked up as a named port in the target Pod's container ports. If this is not 
specified, the value of the 'port' field is used. |
-| service.sessionAffinity | string | `nil` | The session affinity for the 
service. Valid values are: None, ClientIP. The default value is None. ClientIP 
enables sticky sessions based on the client's IP address. This is generally 
beneficial to Polaris deployments, but some testing may be required in order to 
make sure that the load is distributed evenly among the pods. Also, this 
setting affects only internal clients, not external ones. If Ingress is 
enabled, it is recommended to set sessionAffinity to None. |
-| service.trafficDistribution | string | `nil` | The traffic distribution 
field provides another way to influence traffic routing within a Kubernetes 
Service. While traffic policies focus on strict semantic guarantees, traffic 
distribution allows you to express preferences such as routing to topologically 
closer endpoints. The only valid value is: PreferClose. The default value is 
implementation-specific. |
-| service.type | string | `"ClusterIP"` | The type of service to create. Valid 
values are: ExternalName, ClusterIP, NodePort, and LoadBalancer. The default 
value is ClusterIP. |
-| serviceAccount.annotations | object | `{}` | Annotations to add to the 
service account. |
-| serviceAccount.create | bool | `true` | Specifies whether a service account 
should be created. |
-| serviceAccount.name | string | `""` | The name of the service account to 
use. If not set and create is true, a name is generated using the fullname 
template. |
-| serviceMonitor.enabled | bool | `true` | Specifies whether a ServiceMonitor 
for Prometheus operator should be created. |
-| serviceMonitor.interval | string | `""` | The scrape interval; leave empty 
to let Prometheus decide. Must be a valid duration, e.g. 1d, 1h30m, 5m, 10s. |
-| serviceMonitor.labels | object | `{}` | Labels for the created 
ServiceMonitor so that Prometheus operator can properly pick it up. |
-| serviceMonitor.metricRelabelings | list | `[]` | Relabeling rules to apply 
to metrics. Ref 
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config.
 |
-| storage | object | 
`{"secret":{"awsAccessKeyId":null,"awsSecretAccessKey":null,"gcpToken":null,"gcpTokenLifespan":null,"name":null}}`
 | Storage credentials for the server. If the following properties are unset, 
default credentials will be used, in which case the pod must have the necessary 
permissions to access the storage. |
-| storage.secret | object | 
`{"awsAccessKeyId":null,"awsSecretAccessKey":null,"gcpToken":null,"gcpTokenLifespan":null,"name":null}`
 | The secret to pull storage credentials from. |
-| storage.secret.awsAccessKeyId | string | `nil` | The key in the secret to 
pull the AWS access key ID from. Only required when using AWS. |
-| storage.secret.awsSecretAccessKey | string | `nil` | The key in the secret 
to pull the AWS secret access key from. Only required when using AWS. |
-| storage.secret.gcpToken | string | `nil` | The key in the secret to pull the 
GCP token from. Only required when using GCP. |
-| storage.secret.gcpTokenLifespan | string | `nil` | The key in the secret to 
pull the GCP token expiration time from. Only required when using GCP. Must be 
a valid ISO 8601 duration. The default is PT1H (1 hour). |
-| storage.secret.name | string | `nil` | The name of the secret to pull 
storage credentials from. |
-| tasks | object | `{"maxConcurrentTasks":null,"maxQueuedTasks":null}` | 
Polaris asynchronous task executor configuration. |
-| tasks.maxConcurrentTasks | string | `nil` | The maximum number of concurrent 
tasks that can be executed at the same time. The default is the number of 
available cores. |
-| tasks.maxQueuedTasks | string | `nil` | The maximum number of tasks that can 
be queued up for execution. The default is Integer.MAX_VALUE. |
-| tolerations | list | `[]` | A list of tolerations to apply to polaris pods. 
See 
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/. |
-| tracing.attributes | object | `{}` | Resource attributes to identify the 
polaris service among other tracing sources. See 
https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/#service.
 If left empty, traces will be attached to a service named "Apache Polaris"; to 
change this, provide a service.name attribute here. |
-| tracing.enabled | bool | `false` | Specifies whether tracing for the polaris 
server should be enabled. |
-| tracing.endpoint | string | `"http://otlp-collector:4317"` | The collector 
endpoint URL to connect to (required). The endpoint URL must have either the 
http:// or the https:// scheme. The collector must talk the OpenTelemetry 
protocol (OTLP) and the port must be its gRPC port (by default 4317). See 
https://quarkus.io/guides/opentelemetry for more information. |
-| tracing.sample | string | `"1.0d"` | Which requests should be sampled. Valid 
values are: "all", "none", or a ratio between 0.0 and "1.0d" (inclusive). E.g. 
"0.5d" means that 50% of the requests will be sampled. Note: avoid entering 
numbers here, always prefer a string representation of the ratio. |
+| Key | Type | Default                                                         
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                        | Description                           
                                                                                
                                                                                
                                      
                                                                                
                                                                                
                                                                         |

Review Comment:
   It looks like the pipe characters are vertically aligned now, which appears 
as if every line changed.  If you look at the diff in Github while ticking the 
`Hide whitespace` checkbox, only a single line appears as changed.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@polaris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to