Conversation
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Techassi
moved this from Development: In Progress
to Development: Waiting for Review
in Stackable Engineering
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Techassi
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
Co-authored-by: Lars Francke <lars.francke@stackable.tech>
NickLarsenNZ
left a comment
NickLarsenNZ
left a comment
There was a problem hiding this comment.
Been over it, left some comments.
| [#airflow-removals-26_3_0] | ||
| ===== Apache Airflow | ||
|
|
||
| *Breaking:* Users of the `EXPERIMENTAL_FILE_HEADER` and `EXPERIMENTAL_FILE_FOOTER` fields who rely on `AUTH_OID` from the `flask_appbuilder.const` import must switch to `AUTH_OAUTH`. |
There was a problem hiding this comment.
This applies to Superset as well.
There was a problem hiding this comment.
Moved in ab1788b. But this still doesn't mention EXPERIMENTAL_FILE_HEADER and EXPERIMENTAL_FILE_FOOTER which I guess should be added.
| See https://github.com/stackabletech/kafka-operator/pull/933[kafka-operator#933]. | ||
| -- | ||
| * There is a https://github.com/kubernetes/kubernetes/issues/137409[known issue] with the feature gate https://github.com/kubernetes/kubernetes/pull/133153[MaxUnavailableStatefulSet] that is enabled by default as a beta feature in Kubernetes 1.35. | ||
| This issue affects all SDP operators, especially the Trino operator. + |
There was a problem hiding this comment.
We should probably explain why especially Trino.
There was a problem hiding this comment.
Hopefully @razvan can elaborate on this as he was the one who found this problem.
There was a problem hiding this comment.
Trino basically requires catalogs to be useful in any use case and so people are most likely to have this problem. I don't think it's worth elaborating. I named it explicitly so that people using Trino know about it.
There was a problem hiding this comment.
@NickLarsenNZ are you fine with @razvan's answer? What is our way forward?
Co-authored-by: Nick <10092581+NickLarsenNZ@users.noreply.github.com> Co-authored-by: Malte Sander <malte.sander.it@gmail.com>
| * 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). | ||
| + | ||
| -- | ||
| Statically provided user/group information and coarse-grained 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. |
There was a problem hiding this comment.
So, I was part of these discussions and I think I know what's meant here. For those with only a little NiFi knowledge this might be hard to parse or hard to see whether this is relevant for them.
There was a problem hiding this comment.
This refers to situations where the users/groups are fetched from a backend (e.g. Entra, where the user Ids are known), but where some initial permissions should be "fixed" at start-up time, so that at least known users can have permissions to e.g. edit the default pane.
There was a problem hiding this comment.
e.g. in this example we supply an authorizations.xml where some permissions are already set for the admin user on the root process group (the actual process group UUID will be used in place of the placeholder)
| * Driver pods are now garbage collected when the Spark application is finished. | ||
| Previously, driver pods created by the submit job would be left hanging even after the job has been deleted. | ||
| Fixed in https://github.com/stackabletech/spark-k8s-operator/pull/649[spark-k8s-operator#649]. | ||
| * Fix application pod specifications when both the history server and the S3 connection reference the same SecretClass object. |
There was a problem hiding this comment.
Everywhere else we use the "Fixed" (past), this is using a different form. Not super important.
There was a problem hiding this comment.
I would say this is fine, because it still says "fixed" two lines below.
Co-authored-by: Lars Francke <lars.francke@stackable.tech>
7 participants
Release Notes for SDP 26.3.0
Caution
Please assign the applicable
scheduled-for/26.3.0label.Tip
Release note compilation tasks
Optionally check the Changelogs in case release notes were missedUpgrade guide: List removed operators (if there are any)Each of the following tasks focuses on a specific goal and should be done once the items above have been completed.
Release note review tasks