Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13317
---
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 ena
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-222064507
Merging in master/2.0.
---
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
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221950905
So when I was skimming it last night, it looked like it also drops "a and"
to "and" (which is good) but we might also want to mention.
---
If your project is set up fo
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221855988
As a grammar pedant, I approve, even though this is does end up touching a
lot of files. It's helpful to just say in the title that the change is "a ->
an" fixes but no
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221814415
Merged build finished. Test PASSed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221814418
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221814174
**[Test build #59352 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59352/consoleFull)**
for PR 13317 at commit
[`230c801`](https://g
Github user zhengruifeng commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221803163
@holdenk Thanks. Good night.
---
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 n
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221802092
Oh I think the MiMa test failures are spurious. Personally I'm going to go
to sleep and trigger a test again in the morning.
---
If your project is set up for it, you
Github user zhengruifeng commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221801013
@holdenk Excuse me, How to deal with MiMa test failures? It seems caused
by change in `core`
---
If your project is set up for it, you can reply to this email an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221796634
**[Test build #59357 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59357/consoleFull)**
for PR 13317 at commit
[`380fdea`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221796650
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221796648
Merged build finished. Test FAILed.
---
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 projec
Github user zhengruifeng commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221795573
@holdenk Yes. I use cmd like this `grep -in ' a [aeiou]'
mllib/src/main/scala/org/apache/spark/ml/*/*scala`
to generate potential wrong lines.
---
If your pr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221794885
**[Test build #59357 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59357/consoleFull)**
for PR 13317 at commit
[`380fdea`](https://gi
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221793459
Also if this was created by a regex or similar it might be useful for
review to also mention the rule that was applied to make the change.
---
If your project is set u
Github user zhengruifeng commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221792040
@holdenk Thanks. I think you are right. I will revert `an one-xxx` to `a
one-xxx`.
---
If your project is set up for it, you can reply to this email and have your
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221791122
Also, your change seems to have made a few odd changes "an one way" which
sounds odd, generally "a one way" is considered sounding "better" (I'm a bit
fuzzy on the exac
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221791117
**[Test build #59352 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59352/consoleFull)**
for PR 13317 at commit
[`230c801`](https://gi
Github user zhengruifeng commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221790963
@holdenk Thanks. I have fixed this. and run `lint-java` to check java file.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13317#discussion_r64698017
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -105,7 +105,7 @@ private[spark] abstract class MapOutputTracker(conf:
SparkConf)
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221790462
So it seems that in a few places adding the extra character has pushed it
over the 100. You should probably run the linter explicitly if you have it
disabled by default
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221789832
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221789830
**[Test build #59351 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59351/consoleFull)**
for PR 13317 at commit
[`cff3aa8`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221789833
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13317#issuecomment-221789634
**[Test build #59351 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59351/consoleFull)**
for PR 13317 at commit
[`cff3aa8`](https://gi
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/13317
[MINOR] Fix Typos
## What changes were proposed in this pull request?
`a` -> `an`
## How was this patch tested?
local build
You can merge this p
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-220521732
@srowen we should backport the doc fixes into branch-2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13078
---
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 ena
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13078#discussion_r63292985
--- Diff: mllib/src/main/scala/org/apache/spark/ml/ann/Layer.scala ---
@@ -64,8 +64,9 @@ private[ann] trait Layer extends Serializable {
* @return the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218950522
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218950521
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218950439
**[Test build #58537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58537/consoleFull)**
for PR 13078 at commit
[`9b2a5aa`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218942530
**[Test build #58537 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58537/consoleFull)**
for PR 13078 at commit
[`9b2a5aa`](https://gi
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13078#discussion_r63128336
--- Diff: mllib/src/main/scala/org/apache/spark/ml/ann/Layer.scala ---
@@ -64,8 +64,9 @@ private[ann] trait Layer extends Serializable {
* @retur
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13078#discussion_r63128009
--- Diff: mllib/src/main/scala/org/apache/spark/ml/ann/BreezeUtil.scala ---
@@ -55,7 +55,7 @@ private[ann] object BreezeUtil {
* @param y y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218834997
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218834995
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218834686
**[Test build #58497 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58497/consoleFull)**
for PR 13078 at commit
[`2d9a090`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218812765
**[Test build #58497 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58497/consoleFull)**
for PR 13078 at commit
[`2d9a090`](https://gi
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218811368
jenkins, test this please
---
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 ha
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218809524
jenkins, test this please
---
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 ha
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13078#discussion_r63038100
--- Diff: mllib/src/main/scala/org/apache/spark/ml/ann/BreezeUtil.scala ---
@@ -55,7 +55,7 @@ private[ann] object BreezeUtil {
* @param y y
*/
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13078#discussion_r63038154
--- Diff: mllib/src/main/scala/org/apache/spark/ml/ann/Layer.scala ---
@@ -64,8 +64,9 @@ private[ann] trait Layer extends Serializable {
* @return the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218780878
Merged build finished. Test FAILed.
---
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 projec
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218781007
i will retrigger this build once maintenance is over.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218780880
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13078#issuecomment-218766614
**[Test build #58488 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58488/consoleFull)**
for PR 13078 at commit
[`2d9a090`](https://gi
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/13078
[MINOR] Fix Typos
## What changes were proposed in this pull request?
Fix several typos in ML and SQL
## How was this patch tested?
manual tests
You can merge this
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201917668
Thank you, @srowen .
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11968
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201785037
Merged to master
---
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 featu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201604174
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201604171
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201603534
**[Test build #54221 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54221/consoleFull)**
for PR 11968 at commit
[`e11482a`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201598594
Merged build finished. Test PASSed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201598597
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201597966
**[Test build #54217 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54217/consoleFull)**
for PR 11968 at commit
[`534b202`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201528990
**[Test build #54221 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54221/consoleFull)**
for PR 11968 at commit
[`e11482a`](https://gi
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11968#issuecomment-201528379
@JoshRosen . Now, this PR only contains removing unused imports and fixing
java-lint errors.
---
If your project is set up for it, you can reply to this email an
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-192003831
Thank you, @srowen !
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11481
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-192001101
Merged to master
---
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 featu
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191968452
Finally, it passed.
I filed the Kinesis issue as
[SPARK-13655](https://issues.apache.org/jira/browse/SPARK-13655), too.
---
If your project is set up for it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191960929
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191960926
Merged build finished. Test PASSed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191960415
**[Test build #52402 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52402/consoleFull)**
for PR 11481 at commit
[`3cffee2`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191896090
**[Test build #52402 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52402/consoleFull)**
for PR 11481 at commit
[`3cffee2`](https://gi
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191894607
retest this please.
---
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191893626
Thank you for confirming. I'll avoid that in this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191876319
**[Test build #2608 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2608/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://g
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191811582
Yeah, I'm certain it's not this PR as it only changes a test name in the
kinesis module. Something's wrong with the tests there. I'm not sure what do
with this one; unle
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191762447
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191762449
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191762388
**[Test build #52389 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52389/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191672931
**[Test build #52389 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52389/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191671137
Jenkins, test this please
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191670305
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191670308
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191670172
**[Test build #52369 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52369/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://g
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191633263
Hi, @sarutak and @rxin .
three builds hanged at the same test
**WithAggregationKinesisBackedBlockRDDSuite**.
The first build fails due to timeout, the othe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191597133
Merged build finished. Test FAILed.
---
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191597134
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191597050
**[Test build #52348 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52348/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://g
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191588479
Thank you for your advice!
Is the magic word of a committer **Jenkins, test this please** and **ok to
test** then?
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191586618
**[Test build #52369 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52369/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://gi
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191586570
@dongjoon-hyun Once a commiter trigger a test, you can trigger another one
by yourself in the same PR by saying like "retest this please" .
---
If your project is set
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191582841
Oh, thank you for re-triggering.
---
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 d
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191577833
**[Test build #2604 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2604/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://g
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191577290
Hi, @sarutak and @rxin .
**WithAggregationKinesisBackedBlockRDDSuite** took about 2 hours and still
is running.
The following is the last part of Jenk
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191551076
Thank you, @sarutak and @rxin !
---
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 do
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191538377
LGTM pending tests
---
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 featu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191536743
**[Test build #52348 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52348/consoleFull)**
for PR 11481 at commit
[`dd43417`](https://gi
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191535651
ok to test.
---
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
e
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191534879
Can one of the admins verify this patch?
---
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 p
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11481#issuecomment-191534769
Since it's not about documents and contains testcase name typo, so I
couldn't choose `DOCS` as component name.
---
If your project is set up for it, you can rep
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/11481
[MINOR] Fix typos in comments and testcase name of code
## What changes were proposed in this pull request?
This PR fixes typos in comments and testcase name of code.
## How
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10636
---
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 ena
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/10636#discussion_r49051693
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/json/JSONRelation.scala
---
@@ -68,29 +68,12 @@ private[sql] class JSONR
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10636#discussion_r49049305
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/json/JSONRelation.scala
---
@@ -68,29 +68,12 @@ private[sql] class JSONRelati
1 - 100 of 401 matches
Mail list logo
