Github user vanzin commented on a diff in the pull request:

    https://github.com/apache/spark/pull/21669#discussion_r223514310
  
    --- Diff: 
resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/features/HadoopConfExecutorFeatureStep.scala
 ---
    @@ -0,0 +1,52 @@
    +/*
    + * 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.spark.deploy.k8s.features
    +
    +import io.fabric8.kubernetes.api.model.HasMetadata
    +
    +import org.apache.spark.deploy.k8s.{KubernetesConf, 
KubernetesExecutorSpecificConf, SparkPod}
    +import org.apache.spark.deploy.k8s.Constants._
    +import org.apache.spark.deploy.k8s.features.hadooputils.HadoopBootstrapUtil
    +import org.apache.spark.internal.Logging
    +
    + /**
    +  * This step is responsible for bootstraping the container with ConfigMaps
    +  * containing Hadoop config files mounted as volumes and an ENV variable
    +  * pointed to the mounted file directory.
    +  */
    +private[spark] class HadoopConfExecutorFeatureStep(
    +  kubernetesConf: KubernetesConf[KubernetesExecutorSpecificConf])
    --- End diff --
    
    nit: params need extra indentation. (I've pointed this out in other places 
I'm sure, can you go through all your change and fix all the style issues that 
have been pointed out?)


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to