dimas-b commented on code in PR #3281:
URL: https://github.com/apache/polaris/pull/3281#discussion_r2631301007


##########
persistence/relational-jdbc/src/main/java/org/apache/polaris/persistence/relational/jdbc/JdbcMetaStoreManagerFactory.java:
##########
@@ -196,15 +196,20 @@ public Map<String, BaseResult> 
purgeRealms(Iterable<String> realms) {
 
     for (String realm : realms) {
       RealmContext realmContext = () -> realm;
-      PolarisMetaStoreManager metaStoreManager = 
getOrCreateMetaStoreManager(realmContext);
-      BasePersistence session = getOrCreateSession(realmContext);
-
-      PolarisCallContext callContext = new PolarisCallContext(realmContext, 
session);
-      BaseResult result = metaStoreManager.purge(callContext);
-      results.put(realm, result);
-
-      sessionSupplierMap.remove(realm);
-      metaStoreManagerMap.remove(realm);
+      try {
+        PolarisMetaStoreManager metaStoreManager = 
getOrCreateMetaStoreManager(realmContext);
+        BasePersistence session = getOrCreateSession(realmContext);
+
+        PolarisCallContext callContext = new PolarisCallContext(realmContext, 
session);
+        BaseResult result = metaStoreManager.purge(callContext);
+        results.put(realm, result);
+
+        sessionSupplierMap.remove(realm);
+        metaStoreManagerMap.remove(realm);
+      } catch (IllegalStateException e) {
+        // Realm is not bootstrapped, return a failed result
+        results.put(realm, new 
BaseResult(BaseResult.ReturnStatus.ENTITY_NOT_FOUND, e.getMessage()));

Review Comment:
   Hi @flyrain , the logic in your _message_ LGTM, but the logic in the _code_ 
is not specific enough, I'm afraid. 
   
   Catching `IllegalStateException` does not necessarily mean that the failure 
is due to realm not having been bootstrapped.
   
   Is it possible to make this change more specific to the bootstrap use case?



-- 
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]

Reply via email to