You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/partials/release-notes/release-26.3.adoc
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,14 +204,14 @@ See the xref:nifi:usage_guide/security.adoc#authorization[security usage guide]
204
204
--
205
205
* There are cases where customers may wish to provide static authorization files (users.xml, authorizer.xml, authorizations.xml) instead of fetching the data dynamically (for instance, when collecting user and group data from AD/Entra).
206
206
Statically provided user/group information and rough-granular permissions are honoured automatically (as long as the UUIDs match those available in the backend), but for the initial process group this has to be done by a callback mechanism so that the authorizations can be updated after the flow has been registered.
207
-
The Nifi images have been patched for versions 2.4.0 and 2.6.0 to implement this.
208
-
See https://github.com/stackabletech/nifi-operator/issues/862[nifi-operator#862].
207
+
The Nifi images have been patched for versions 2.4.0 and 2.6.0 to support this.
208
+
Implemented in https://github.com/stackabletech/nifi-operator/issues/862[nifi-operator#862].
209
209
210
210
===== Apache Spark
211
211
212
212
Spark application jobs can now have pod/node affinities.
213
213
Previously only the application driver and executors had a dedicated field for this purpose.
214
-
See https://github.com/stackabletech/spark-k8s-operator/issues/639[spark-k8s-operator#639].
214
+
Implemented in https://github.com/stackabletech/spark-k8s-operator/issues/639[spark-k8s-operator#639].
215
215
216
216
===== Open Policy Agent
217
217
@@ -222,16 +222,28 @@ See https://github.com/stackabletech/spark-k8s-operator/issues/639[spark-k8s-ope
222
222
Conversion between v1alpha1 and v1alpha2 is handled automatically by default.
223
223
Implemented in https://github.com/stackabletech/opa-operator/pull/801[opa-operator#801].
224
224
225
+
[#trino-improvements-26_3_0]
225
226
===== Trino
226
227
227
-
*Breaking:* The operator no longer sets `opa.policy.column-masking-uri` in `access-control.properties` but `opa.policy.batch-column-masking-uri` instead, allowing Trino to fetch multiple column masks in a single request.
228
-
This therefore now requires a `batchColumnMasks` rule to be present in the OPA Trino rules, when using the default URI set by the trino-operator.
228
+
* *Breaking:* The operator no longer sets `opa.policy.column-masking-uri` in `access-control.properties` but `opa.policy.batch-column-masking-uri` instead, allowing Trino to fetch multiple column masks in a single request.
229
+
This therefore now requires a `batchColumnMasks` rule to be present in the OPA Trino rules, when using the default URI set by the trino-operator. +
230
+
The above default can be disabled with the new enableColumnMasking field in the opa configuration in authorization
231
+
+
232
+
--
233
+
[WARNING]
234
+
====
235
+
The `opa` field under `authorization` is now a mandatory enum variant instead of being optional.
236
+
====
229
237
230
-
* The above default can be disabled with the new enableColumnMasking field in the opa configuration in authorization
231
-
* *Breaking:* The field opa in authorization is now a mandatory enum variant instead of being optional
232
-
* Quick note: Use `spec.clusterConfig.authorization.opa.enableColumnMasking: false` instead of `batchColumnMasks = []`
238
+
[TIP]
239
+
====
240
+
It is recommended to use `spec.clusterConfig.authorization.opa.enableColumnMasking: false` instead of `batchColumnMasks = []`.
241
+
====
233
242
234
-
See https://github.com/stackabletech/trino-operator/issues/814[trino-operator#814].
243
+
Implemented in https://github.com/stackabletech/trino-operator/issues/814[trino-operator#814].
244
+
--
245
+
* The `spec.connector.iceberg.metastore` field in TrinoCatalog is now optional, as Iceberg also supports other catalogs, such as a REST catalog, which (currently) can only be added using configOverrides.
246
+
Implemented in https://github.com/stackabletech/trino-operator/pull/841[trino-operator#841].
0 commit comments