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

    https://github.com/apache/spark/pull/9182#discussion_r43281460
  
    --- Diff: 
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
 ---
    @@ -17,17 +17,17 @@
     
     package org.apache.spark.scheduler.cluster
     
    -import scala.collection.mutable.ArrayBuffer
    -import scala.concurrent.{Future, ExecutionContext}
    +import scala.concurrent.{ExecutionContext, Future}
    +import scala.util.control.NonFatal
    +
    +import org.apache.hadoop.yarn.api.records.{ApplicationAttemptId, 
ApplicationId}
     
    -import org.apache.spark.{Logging, SparkContext}
     import org.apache.spark.rpc._
    -import org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages._
     import org.apache.spark.scheduler._
    +import org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages._
     import org.apache.spark.ui.JettyUtils
    -import org.apache.spark.util.{ThreadUtils, RpcUtils}
    -
    -import scala.util.control.NonFatal
    +import org.apache.spark.util.{RpcUtils, ThreadUtils}
    +import org.apache.spark.{Logging, SparkContext}
    --- End diff --
    
    uh oh, this looks like IDEA may be imposting a different sort order than 
expected, especially on `{` chars.
    
    This is what the IDE-generated order looks like, based on the instructions 
in the spark style guide:
    
    ```
    import scala.concurrent.{ExecutionContext, Future}
    import scala.util.control.NonFatal
    
    import org.apache.hadoop.yarn.api.records.{ApplicationAttemptId, 
ApplicationId}
    
    import org.apache.spark.rpc._
    import org.apache.spark.scheduler._
    import org.apache.spark.scheduler.cluster.CoarseGrainedClusterMessages._
    import org.apache.spark.ui.JettyUtils
    import org.apache.spark.util.{RpcUtils, ThreadUtils}
    import org.apache.spark.{Logging, SparkContext}
    ```
    
    What's it getting wrong? as in "what will I have to review all my source 
files for"?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Reply via email to