huaxingao commented on code in PR #4659: URL: https://github.com/apache/polaris/pull/4659#discussion_r3406945421
########## polaris-core/src/main/java/org/apache/polaris/core/persistence/IdempotencyStoreFactory.java: ########## @@ -0,0 +1,39 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.polaris.core.persistence; + +import com.google.common.annotations.Beta; +import org.apache.polaris.core.context.RealmContext; + +/** + * Factory for per-realm {@link IdempotencyStore} instances. + * + * <p>This SPI is intentionally kept separate from {@link MetaStoreManagerFactory}: handler-level + * idempotency persistence is conceptually independent from the catalog metastore, and a deployment + * may want to back it with a different store (e.g. a dedicated PostgreSQL instance) than the + * primary metastore. Backends register implementations with {@link + * io.smallrye.common.annotation.Identifier} matching the {@code polaris.idempotency.type} + * configuration value. + * + * <p>Returned instances must be safe to share across threads. + */ +@Beta +public interface IdempotencyStoreFactory { + + /** Returns the {@link IdempotencyStore} to use for the given realm. */ + IdempotencyStore getOrCreateIdempotencyStore(RealmContext realmContext); Review Comment: Correction to my earlier reply. I took the core of your proposal: a request-scoped producer in runtime/service now hands IdempotencyHandlerSupport a plain IdempotencyStore — no factory reference, no lazy init. I kept the backend factory, though. Dropping it entirely breaks the Admin Tool build: admin pulls in relational-jdbc (runtimeOnly) but has no request scope, so a CDI bean needing RealmContext is unsatisfiable there (quarkusAppPartsBuild → UnsatisfiedResolutionException). The realm has to arrive as a method arg — same as JdbcMetaStoreManagerFactory. So the factory stays as the realm-agnostic, @Identifier-keyed backend contract, consumed by the producer; it's no longer exposed to the handler. If the concern is that it's reusable rather than local, I'm happy to narrow its visibility — but I don't see how to resolve the backend with RealmContext on the admin side without a realm-as-param contract. LMK if you see a way around it. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
