JingGe commented on a change in pull request #17995:
URL: https://github.com/apache/flink/pull/17995#discussion_r761994222



##########
File path: 
flink-runtime/src/main/java/org/apache/flink/runtime/dispatcher/ConfigurationNotAllowedError.java
##########
@@ -0,0 +1,50 @@
+/*
+ * 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.flink.runtime.dispatcher;
+
+import org.apache.flink.annotation.Internal;
+
+/**
+ * If {@link 
org.apache.flink.configuration.DeploymentOptions#ALLOW_CLIENT_JOB_CONFIGURATIONS}
 is
+ * disabled this error denotes the not allowed configuration.
+ */
+@Internal
+public class ConfigurationNotAllowedError implements JobValidationError {

Review comment:
       Speaking of "Program logic that is buggy has to be expected from Flink's 
perspective", if I understood you correctly, agree with you, should use checked 
exception. The bottom line guideline from official Java tutorial is: "If a 
client can reasonably be expected to recover from an exception, make it a 
checked exception. If a client cannot do anything to recover from the 
exception, make it an unchecked exception." 
https://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html




-- 
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...@flink.apache.org

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


Reply via email to