SuccessChanges

Summary

  1. [SPARK-30409][TEST][FOLLOWUP][HOTFIX] Remove dangling (details)
  2. [SPARK-28752][BUILD][DOCS][FOLLOW-UP] Render examples imported from (details)
Commit 361583d1f5bb7bc2eb87395cf52f2182352e25cb by dhyun
[SPARK-30409][TEST][FOLLOWUP][HOTFIX] Remove dangling
JSONBenchmark-jdk11-results.txt
### What changes were proposed in this pull request?
This PR removes a dangling test result,
`JSONBenchmark-jdk11-results.txt`. This causes a case-sensitive issue on
Mac.
```
$ git clone https://gitbox.apache.org/repos/asf/spark.git spark-gitbox
Cloning into 'spark-gitbox'... remote: Counting objects: 671717, done.
remote: Compressing objects: 100% (258021/258021), done. remote: Total
671717 (delta 329181), reused 560390 (delta 228097) Receiving objects:
100% (671717/671717), 149.69 MiB | 950.00 KiB/s, done. Resolving deltas:
100% (329181/329181), done. Updating files: 100% (16090/16090), done.
warning: the following paths have collided (e.g. case-sensitive paths on
a case-insensitive filesystem) and only one from the same colliding
group is in the working tree:
  'sql/core/benchmarks/JSONBenchmark-jdk11-results.txt'
'sql/core/benchmarks/JsonBenchmark-jdk11-results.txt'
```
### Why are the changes needed?
Previously, since the file name didn't match with `object
JSONBenchmark`, it made a confusion when we ran the benchmark. So,
4e0e4e51c4 renamed `JSONBenchmark` to `JsonBenchmark`. However, at the
same time frame, https://github.com/apache/spark/pull/26003 regenerated
this file.
Recently, https://github.com/apache/spark/pull/27078 regenerates the
results with the correct file name, `JsonBenchmark-jdk11-results.txt`.
So, we can remove the old one.
### Does this PR introduce any user-facing change?
No. This is a test result.
### How was this patch tested?
Manually check the following correctly generated files in the master.
And, check this PR removes the dangling one.
-
https://github.com/apache/spark/blob/master/sql/core/benchmarks/JsonBenchmark-results.txt
-
https://github.com/apache/spark/blob/master/sql/core/benchmarks/JsonBenchmark-jdk11-results.txt
Closes #27180 from dongjoon-hyun/SPARK-REMOVE.
Authored-by: Dongjoon Hyun <dhyun@apple.com> Signed-off-by: Dongjoon
Hyun <dhyun@apple.com>
The file was removedsql/core/benchmarks/JSONBenchmark-jdk11-results.txt
Commit 150d49372f6dfe051b8049e4fe0356ee51cb547c by gurwls223
[SPARK-28752][BUILD][DOCS][FOLLOW-UP] Render examples imported from
Jekyll properly via Rouge
### What changes were proposed in this pull request?
This PR proposes to use Pygment compatible format by Rouge. As of
https://github.com/apache/spark/pull/26521, we use Rouge instead of
Pygment wrapper in Ruby. Rouge claims Pygment compatibility; and we
should output as Pygment does.
```ruby Rouge::Formatters::HTMLPygments.new(formatter)
```
wraps codes with `<div class="highlight"><pre>...` properly.
### Why are the changes needed?
To keep the documentation pretty and not broken.
### Does this PR introduce any user-facing change?
Theoretically, no.
This is rather a regression fix in documentation (that happens only by
https://github.com/apache/spark/pull/26521 in master). See the malformed
doc in preview -
https://spark.apache.org/docs/3.0.0-preview2/sql-pyspark-pandas-with-arrow.html
### How was this patch tested?
Manually built the doc.
**Before:**
![Screen Shot 2020-01-13 at 10 21 28
AM](https://user-images.githubusercontent.com/6477701/72229159-ba766a80-35ef-11ea-9a5d-9583448e7c1c.png)
**After:**
![Screen Shot 2020-01-13 at 10 26 33
AM](https://user-images.githubusercontent.com/6477701/72229157-b34f5c80-35ef-11ea-8b3a-492e8aa0f82a.png)
Closes #27182 from HyukjinKwon/SPARK-28752-followup.
Authored-by: HyukjinKwon <gurwls223@apache.org> Signed-off-by:
HyukjinKwon <gurwls223@apache.org>
The file was modifieddocs/_plugins/include_example.rb (diff)