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
### 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
$ git clone 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:
### 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, regenerated
this file.
Recently, 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.
Closes #27180 from dongjoon-hyun/SPARK-REMOVE.
Authored-by: Dongjoon Hyun <> Signed-off-by: Dongjoon
Hyun <>
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, we use Rouge instead of
Pygment wrapper in Ruby. Rouge claims Pygment compatibility; and we
should output as Pygment does.
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 in master). See the malformed
doc in preview -
### How was this patch tested?
Manually built the doc.
![Screen Shot 2020-01-13 at 10 21 28
![Screen Shot 2020-01-13 at 10 26 33
Closes #27182 from HyukjinKwon/SPARK-28752-followup.
Authored-by: HyukjinKwon <> Signed-off-by:
HyukjinKwon <>
The file was modifieddocs/_plugins/include_example.rb (diff)