[SPARK-12692][BUILD][CORE] Scala style: Fix the style violation (Space before ",")

[sarutak]

Fix the style violation (space before , and :).
This PR is a followup for #10643

[sarutak]

Ah, we also need to modify MimaExclude.scala.

[rxin]

Why don't we reset this change and just turn the rule off here-- otherwise the huge mima exclusion is pretty annoying.

[sarutak]

It's reasonable. I'll do it.

[sarutak]

So should we reset the change in flume/sink/Logging?

[rxin]

It is less big of a deal there since it is already done and it is small. But feel free to do whatever you deem fit.

[sarutak]

O.K, it's less big deal. I'll only reset for this change.

[SparkQA]

Test build #49217 has finished for PR 10719 at commit e2202c8.

• This patch fails to build.
• This patch merges cleanly.
• This patch adds the following public classes (experimental):
  • class ComplexFutureAction[T](run: JobSubmitter => Future[T])
  • class RangePartitioner[K: Ordering: ClassTag, V](
  • class SequenceFileRDDFunctions[K <% Writable: ClassTag, V <% Writable: ClassTag](
  • class OpenHashMap[K: ClassTag, @specialized(Long, Int, Double) V: ClassTag](
  • class KVArraySortDataFormat[K, T <: AnyRef: ClassTag] extends SortDataFormat[K, Array[T]]

[SparkQA]

Test build #49221 has finished for PR 10719 at commit fc95915.

• This patch fails MiMa tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Test build #49234 has finished for PR 10719 at commit e953d13.

• This patch fails MiMa tests.
• This patch merges cleanly.
• This patch adds no public classes.

[sarutak]

The additional mima exclusions are few so I'll add them.

[SparkQA]

Test build #49230 has finished for PR 10719 at commit 5d4b1a9.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Test build #49236 has finished for PR 10719 at commit 9079c27.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[rxin]

I responded here: #10685 (comment)

Pasting the message here too:
@sarutak I actually reverted this change after talking more with Michael and looking at the diffs. The problem is that for colon, in some cases it is really useful to have a space before colon. In particular:

In many cases for type bounds, ti is good to have a space before the colon so it is more clear.
For type descriptions (e.g. variable : Int), it is also often useful to have a space.
I don't know whether it is feasible to actually implement the rules for the general colon, but exclude type description and type bounds. If yes, we should add this enforcement. Otherwise I'd prefer not to have it at all.

For comma, we should always have it (at least I haven't seen a case in which we don't want it yet).

[SparkQA]

Test build #49280 has finished for PR 10719 at commit 284da4b.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[rxin]

I've merged this.