Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16970#discussion_r102290771
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1996,7 +1996,7 @@ class Dataset[T] private[sql](
def
GitHub user actuaryzhang opened a pull request:
https://github.com/apache/spark/pull/17017
[SPARK-19682][SparkR] Issue warning (or error) when subset method "[["
takes vector index
## What changes were proposed in this pull request?
The `[[` method is supposed to take a single
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16499
**[Test build #73226 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73226/testReport)**
for PR 16499 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16970
**[Test build #73225 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73225/testReport)**
for PR 16970 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16989
**[Test build #73224 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73224/testReport)**
for PR 16989 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16989
Jenkins, add to whitelist
---
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
Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/15415
Hi @jkbradley
We can hold the transform code.
> wrap the old AssociationRules code
Do you mean to make transform return the Association Rules DataFrame, like
the currect
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16989
Hi @jinxing64 I posted a comment on jira about the design -- I think this
is a big enough change that its worth discussing the design first. Its fine to
keep working on the code as a demonstration
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16499
**[Test build #73223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73223/testReport)**
for PR 16499 at commit
Github user stp008 commented on the issue:
https://github.com/apache/spark/pull/16629
actually if u turn it off then for each batch new consumer will be created.
For me the solution is to introduce pool of consumers equal to the total count
of concurrent job for example
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16977
**[Test build #73222 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73222/testReport)**
for PR 16977 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16892#discussion_r102282650
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -2031,6 +2051,11 @@ class DAGSchedulerSuite extends SparkFunSuite
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16892#discussion_r102281985
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -1569,24 +1569,44 @@ class DAGSchedulerSuite extends SparkFunSuite
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/10405
@Naresh523 this particular issue doesn't appear to exist in 1.6 because the
change that this fixes went into 2.0
---
If your project is set up for it, you can reply to this email and have your
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16901
sorry responding late to this, but your analysis sounds fine
---
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
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16978
code changes look fine, but is it possible to add a test case to
HistoryServerSuite? I worry nobody is going to think about security / know how
to test it so it may easily get broken.
---
If your
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17011
Yes, this is pretty weird. Especially since I've never seen this test fail
nor heard about anyone else having seen it fail. If you can point out in the
Hadoop code where that discrepancy can occur,
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16955
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16955
Merging to master / 2.1.
---
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
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16923#discussion_r102273608
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -106,21 +106,27 @@ private[hive] class HiveClientImpl(
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/15415#discussion_r102273256
--- Diff: mllib/src/test/scala/org/apache/spark/ml/fpm/FPGrowthSuite.scala
---
@@ -0,0 +1,130 @@
+/*
+ * Licensed to the Apache Software
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/15415#discussion_r102273266
--- Diff: mllib/src/test/scala/org/apache/spark/ml/fpm/FPGrowthSuite.scala
---
@@ -0,0 +1,130 @@
+/*
+ * Licensed to the Apache Software
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/16499#discussion_r102272981
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -813,7 +813,14 @@ private[spark] class BlockManager(
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/16499#discussion_r102271763
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -1018,7 +1025,9 @@ private[spark] class BlockManager(
try {
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16968
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16968
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 feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16985
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73221/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16985
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16985
**[Test build #73221 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73221/testReport)**
for PR 16985 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/17002
Yea @gatorsmile be careful in the future and check the commit hash.
---
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
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16905
If Jenkins is listening to me, that should have allowed you to trigger test
for this PR.
test this please
---
If your project is set up for it, you can reply to this email and have
Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/17014
It's better if we can fix this without breaking API. Let's allow some time
to see if there's a better solution.
Meanwhile, if we have to add the new parameter, can we set some default
value?
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17014#discussion_r102262826
--- Diff: mllib/src/main/scala/org/apache/spark/ml/Predictor.scala ---
@@ -126,9 +129,10 @@ abstract class Predictor[
* and copying parameters into
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks @markhamstra.
I think jenkins needs to be triggered.
---
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
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16905
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
enabled and wishes so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16985
**[Test build #73221 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73221/testReport)**
for PR 16985 at commit
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/16985#discussion_r102245647
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/SortMergeJoinExec.scala
---
@@ -33,8 +33,8 @@ import
Github user Naresh523 commented on the issue:
https://github.com/apache/spark/pull/10405
I'm seeing this issue been fixed in v2.0.0. Is there any possibility to fix
this in v1.6.x ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user Donderia commented on the issue:
https://github.com/apache/spark/pull/10307
Thanks for your kind reply. sorry for the delay in reply
I have fixed this and it working fine. )
On Sat, Feb 18, 2017 at 12:41 AM, Holden Karau
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73218/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73218 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73218/testReport)**
for PR 17011 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73219/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73219/testReport)**
for PR 17014 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17014#discussion_r102205041
--- Diff: mllib/src/main/scala/org/apache/spark/ml/Predictor.scala ---
@@ -126,9 +129,10 @@ abstract class Predictor[
* and copying parameters into
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17011
I don't quite see why it can succeed in listing a file that's not readable,
later in mergeApplicationListing? won't that fail or generate an error already?
Therefore I'm wondering if this is really
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17016
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73220/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17016
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17016
**[Test build #73220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73220/testReport)**
for PR 17016 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102202049
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73216/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73216 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73216/testReport)**
for PR 17013 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17016
**[Test build #73220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73220/testReport)**
for PR 17016 at commit
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/17016
[SPARK-19679][ML] Destroy broadcasted object without blocking
## What changes were proposed in this pull request?
Destroy broadcasted object without blocking
use `find mllib -name
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73206/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73206/testReport)**
for PR 17011 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16971
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16971
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73211/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17015
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17015
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73212/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16971
**[Test build #73211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73211/testReport)**
for PR 16971 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17015
**[Test build #73212 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73212/testReport)**
for PR 17015 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73219 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73219/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73210/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73210 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73210/testReport)**
for PR 17013 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73217/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73217 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73217/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73217 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73217/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73218 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73218/testReport)**
for PR 17011 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17011
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 this feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73216/testReport)**
for PR 17013 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17013
Thanks for your review @maropu.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16990
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16990
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73207/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16990
**[Test build #73207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73207/testReport)**
for PR 16990 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73215/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73215 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73215/testReport)**
for PR 17014 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102182533
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73214/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73214 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73214/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73215 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73215/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73214 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73214/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73213 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73213/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73213/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73213 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73213/testReport)**
for PR 17014 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102177949
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17015
**[Test build #73212 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73212/testReport)**
for PR 17015 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/17015
[SPARK-19678][SQL] remove MetastoreRelation
## What changes were proposed in this pull request?
`MetastoreRelation` is used to represent table relation for hive tables,
and provides
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17015
cc @gatorsmile @sameeragarwal
---
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
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102175873
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102175210
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user HarshSharma8 commented on the issue:
https://github.com/apache/spark/pull/16997
Hello HyukjinKwon,
I have updated the title, i wish you like it, it shows what is there in the
content. And commit has already been made.
---
If your project is set up for it, you can
401 - 500 of 531 matches
Mail list logo
