Skip to content

Conversation

@XN137
Copy link
Contributor

@XN137 XN137 commented Jul 23, 2025

note how all the callers immediately called Supplier.get - it seems like the Supplier has become a leaking implementation detail of the MetaStoreManagerFactory classes.

@github-project-automation github-project-automation bot moved this to PRs In Progress in Basic Kanban Board Jul 23, 2025
@XN137 XN137 marked this pull request as ready for review July 23, 2025 10:33
adutra
adutra previously approved these changes Jul 23, 2025
@github-project-automation github-project-automation bot moved this from PRs In Progress to Ready to merge in Basic Kanban Board Jul 23, 2025
dimas-b
dimas-b previously approved these changes Jul 23, 2025
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: previously the .get() call was outside the synchronized block... not sure it matters, though 🤔

@dimas-b
Copy link
Contributor

dimas-b commented Jul 23, 2025

@XN137 : Changes LGTM. Please resolve conflicts :)

note how all the caller immediately called `get` on the returned `Supplier`.
it seems like the `Supplier` was an leaking implementation detail of the
`MetaStoreManagerFactor` implementations.
@XN137 XN137 dismissed stale reviews from dimas-b and adutra via b58e293 July 23, 2025 21:17
@XN137 XN137 force-pushed the rework-getOrCreateSessionSupplier branch from 18ab8cc to b58e293 Compare July 23, 2025 21:17
@XN137
Copy link
Contributor Author

XN137 commented Jul 23, 2025

rebased after tiny conflicts with 5faa371

Copy link
Member

@snazy snazy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, the Supplier looks like an implementation detail. All call sites immediately called .get() anyways, so I do not see any functional change here, not even a behavior change (@dimas-b's comment in the JDBC part).

@dimas-b dimas-b merged commit ca85339 into apache:main Jul 24, 2025
12 checks passed
@github-project-automation github-project-automation bot moved this from Ready to merge to Done in Basic Kanban Board Jul 24, 2025
@XN137 XN137 deleted the rework-getOrCreateSessionSupplier branch July 24, 2025 14:01
snazy added a commit to snazy/polaris that referenced this pull request Nov 20, 2025
* Extract ResolverFactory from PolarisEntityManager (apache#2148)

`PolarisEntityManager.prepareResolver` was the only place that used the `EntityCache`. By introducing an application-scoped `ResolverFactory` the creation of an `EntityCache` is decided only once in `QuarkusProducers`, which will become the only place where `MetaStoreManagerFactory.getOrCreateEntityCache` gets called.

Note that the little left-over functionality of `PolarisEntityManager` can
be split out to more dedicated interfaces in a follow-up most likely.

* Run standard (sharable) REST Catalog integrations tests with MinIO (apache#2158)

* Run standard (sharable) REST Catalog integrations tests with MinIO

Keep special edge case tests (path style, STS endpoint and
client-side FileIO) in `QuarkusRestCatalogMinIoSpecialIT`.

* fix(deps): update quarkus platform and group (apache#2166)

* fix(deps): update dependency io.smallrye.config:smallrye-config-core to v3.13.4 (apache#2165)

* Simplify checkPolarisServiceBootstrappedForRealm (apache#2162)

* fix(deps): update dependency boto3 to v1.39.12 (apache#2169)

* Improve Realm ID resolution for Quarkus 3.24+ (apache#2163)

In Quarkus 3.24, it is now possible to retrieve context locals inside HttpServerMetricsTagsContributor. This greatly simplifies our RealmIdTagContributor implementation.

It is also now possible to return null from ValueExpressionResolver. This is not a big deal, but still better than returning "".

* chore(deps): update plugin jandex to v2.2.0 (apache#2175)

* Add muti-platform Docker images staging in the release guide (apache#2039)

* fix(deps): update dependency org.apache.commons:commons-text to v1.14.0 (apache#2178)

* Rework getOrCreateSessionSupplier (apache#2161)

note how all the caller immediately called `get` on the returned `Supplier`.
it seems like the `Supplier` was an leaking implementation detail of the
`MetaStoreManagerFactor` implementations.

* Respond with 409 in case of concurrent Namespace update failures instead of 500 (apache#1989)

* NoSQL adoptions

* Last merged commit e9267b6

---------

Co-authored-by: Christopher Lambert <xn137@gmx.de>
Co-authored-by: Dmitri Bourlatchkov <dmitri.bourlatchkov@gmail.com>
Co-authored-by: Mend Renovate <bot@renovateapp.com>
Co-authored-by: Alexandre Dutra <adutra@apache.org>
Co-authored-by: JB Onofré <jbonofre@apache.org>
Co-authored-by: fabio-rizzo-01 <fabio.rizzocascio@jpmorgan.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants