amogh-jahagirdar commented on code in PR #11180:
URL: https://github.com/apache/iceberg/pull/11180#discussion_r1798639774


##########
core/src/main/java/org/apache/iceberg/RESTPlanningMode.java:
##########
@@ -0,0 +1,47 @@
+/*
+ * 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.iceberg;
+
+import java.util.Locale;
+import org.apache.iceberg.relocated.com.google.common.base.Preconditions;
+
+public enum RESTPlanningMode {
+  REQUIRED("required"),
+  SUPPORTED("supported"),
+  UNSUPPORTED("unsupported");

Review Comment:
   Sounds good. After some more thought, my 2c is that I think I'd rather us 
try and get the model + client side changes into 1.7 rather than expand the 
scope with this aspect since it's quite useful without these things defined. 
I'd rather not have client side changes depend on another spec change decision.
   
   For now, I think keeping it simple with a catalog client side property for 
controlling if server side planning is performed is the way forward.
   
   Once the model and client side changes are in, I think it'd make total sense 
to revisit the spec changes you mentioned and these specific planning mode 
changes.
   
   cc @rdblue @danielcweeks for their thoughts.



-- 
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: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to