Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/15264
@HyukjinKwon I agree. Would you have cycles to re-open
https://github.com/apache/spark/pull/14215 by any chance? This is something
that'd be great to have that in 2.2.
---
If your project is
Github user shubhamchopra commented on a diff in the pull request:
https://github.com/apache/spark/pull/14412#discussion_r99190414
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterEndpoint.scala
---
@@ -188,24 +189,45 @@ class BlockManagerMasterEndpoint(
Github user shubhamchopra commented on a diff in the pull request:
https://github.com/apache/spark/pull/14412#discussion_r99189219
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -1152,20 +1185,25 @@ private[spark] class BlockManager(
Github user shubhamchopra commented on a diff in the pull request:
https://github.com/apache/spark/pull/14412#discussion_r99185105
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -1152,20 +1185,25 @@ private[spark] class BlockManager(
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72286/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72286/testReport)**
for PR 16733 at commit
[`1b9e7a9`](https://github.com/apache/spark/commit/1
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16779
@jinxing64 Good catch. Since you are touching this file, could you also
replace other `askWithRetry` in this file with `askSync`?
---
If your project is set up for it, you can reply to this email a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72285/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72285/testReport)**
for PR 16733 at commit
[`352163e`](https://github.com/apache/spark/commit/3
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16781
**[Test build #72288 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72288/testReport)**
for PR 16781 at commit
[`5b49ae0`](https://github.com/apache/spark/commit/5b
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72284/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72284/testReport)**
for PR 16733 at commit
[`76b005e`](https://github.com/apache/spark/commit/7
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16762#discussion_r99178232
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/BroadcastNestedLoopJoinExec.scala
---
@@ -339,6 +340,18 @@ case class BroadcastNe
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16766
I'd second that. I'd be interested to know if this implementation changes
behavior for `coalesce`
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16767
looking good to me. I'll wait for @wangmiao1981 to review.
---
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 no
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16729
hmm.. I'm not sure we could do that because of Apache licensing policy
(unless the owner decides to submit that here).
let me think about this a bit.
---
If your project is set up for
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/16578#discussion_r99174674
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/SelectedField.scala
---
@@ -0,0 +1,76 @@
+/*
+ * Licensed to the Apache
Github user shubhamchopra commented on a diff in the pull request:
https://github.com/apache/spark/pull/14412#discussion_r99174290
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -1131,14 +1131,47 @@ private[spark] class BlockManager(
}
Github user shubhamchopra commented on a diff in the pull request:
https://github.com/apache/spark/pull/14412#discussion_r99174354
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -1131,14 +1131,47 @@ private[spark] class BlockManager(
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16779
**[Test build #3553 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3553/testReport)**
for PR 16779 at commit
[`06efcac`](https://github.com/apache/spark/commit/
Github user actuaryzhang commented on the issue:
https://github.com/apache/spark/pull/16729
@felixcheung The one from statmod will be masked and must be called using
`statmod:tweedie`.
We can copy the whole `tweedie` function from statmod into `SparkR` and
this will avoid the is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16781
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16781
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72287/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16781
**[Test build #72287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72287/testReport)**
for PR 16781 at commit
[`223ce2c`](https://github.com/apache/spark/commit/22
GitHub user squito opened a pull request:
https://github.com/apache/spark/pull/16781
[SPARK-12297][SQL][POC] Hive compatibility for Parquet Timestamps
## What changes were proposed in this pull request?
Hive has very strange behavior when writing timestamps to parquet data.
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/12135
I am fine to create a separate one, but, normally, in Spark SQL, we do not
create a separate JIRA for improving the related test case, if the original
ones are missing.
---
If your project is
Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/16738
@srowen
Thanks a lot. I'll refine : )
---
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 featur
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16780
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 project does not have this feat
GitHub user jinxing64 opened a pull request:
https://github.com/apache/spark/pull/16780
[SPARK-19438] Both reading and updating executorDataMap should be guarded
by CoarseGrainedSchedulerBackend.this.synchronized when handle RegisterExecutor.
## What changes were proposed in this pu
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72283/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72283/testReport)**
for PR 16733 at commit
[`3e603ee`](https://github.com/apache/spark/commit/3
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72286/testReport)**
for PR 16733 at commit
[`1b9e7a9`](https://github.com/apache/spark/commit/1b
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16775
`StringIndexer` and `OneHotEncoder` are just used as example here. The
concept is to have a pipeline with enough long stages.
---
If your project is set up for it, you can reply to this email and ha
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72285/testReport)**
for PR 16733 at commit
[`352163e`](https://github.com/apache/spark/commit/35
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72284/testReport)**
for PR 16733 at commit
[`76b005e`](https://github.com/apache/spark/commit/76
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72281/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16733
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72281/testReport)**
for PR 16733 at commit
[`712b80c`](https://github.com/apache/spark/commit/7
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16778
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
e
Github user DavidArenburg commented on the issue:
https://github.com/apache/spark/pull/16775
Wouldn't it better to Vectorize `StringIndexer` and `OneHotEncoder`? Like
for instance `.na.fill` or `.na.replace` operate over the whole data set at
once instead of running it in a loop? I fe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16778
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72282/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16778
**[Test build #72282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72282/testReport)**
for PR 16778 at commit
[`4a54bb4`](https://github.com/apache/spark/commit/4
Github user nblintao closed the pull request at:
https://github.com/apache/spark/pull/14204
---
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 e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16779
**[Test build #3553 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3553/testReport)**
for PR 16779 at commit
[`06efcac`](https://github.com/apache/spark/commit/0
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16779
CC @zsxwing
---
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 th
Github user mariusvniekerk commented on a diff in the pull request:
https://github.com/apache/spark/pull/16766#discussion_r99132600
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -823,6 +825,17 @@ case class Rep
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16779
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 project does not have this feat
GitHub user jinxing64 opened a pull request:
https://github.com/apache/spark/pull/16779
[SPARK-19437] Rectify spark executor id in HeartbeatReceiverSuite.
## What changes were proposed in this pull request?
The current code in `HeartbeatReceiverSuite`, executorId is set as b
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16778
@srowen, I have few candidates we might have to consider.
My list is almost overlapped with this. So, I have only the ones I
inclusively picked up. I think you already took a look for most of
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/16771
cc @holdenk
---
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 t
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16652
**[Test build #3552 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3552/testReport)**
for PR 16652 at commit
[`c855976`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16777
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72280/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16777
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
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15264
BTW, I just wonder if this PR is closable if we want to do this with more
types :).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16777
**[Test build #72280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72280/testReport)**
for PR 16777 at commit
[`bd0d9f7`](https://github.com/apache/spark/commit/b
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72283/testReport)**
for PR 16733 at commit
[`3e603ee`](https://github.com/apache/spark/commit/3e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16778
**[Test build #72282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72282/testReport)**
for PR 16778 at commit
[`4a54bb4`](https://github.com/apache/spark/commit/4a
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/16778
[BUILD] Close stale PRs
Closes #15736
Closes #16309
Closes #16485
Closes #16502
Closes #16196
Closes #16498
Closes #12380
Closes #16764
You can merge this pull request in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16733
**[Test build #72281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72281/testReport)**
for PR 16733 at commit
[`712b80c`](https://github.com/apache/spark/commit/71
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16744#discussion_r99110527
--- Diff: pom.xml ---
@@ -146,6 +146,8 @@
hadoop2
0.7.1
1.6.2
+
+1.10.61
--- End diff --
This is probab
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16652
**[Test build #3552 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3552/testReport)**
for PR 16652 at commit
[`c855976`](https://github.com/apache/spark/commit/c
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/16767
ping @wangmiao1981 @felixcheung
---
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
ena
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16738
Rather than remove the comment, maybe it's better to clarify it as you say,
to refer to being "completed" rather than "successful". I don't know enough to
evaluate whether you're right about that cha
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16776
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16776
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72279/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16776
**[Test build #72279 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72279/testReport)**
for PR 16776 at commit
[`917fd6e`](https://github.com/apache/spark/commit/9
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16776
cc @gatorsmile @HyukjinKwon @holdenk @MLnick
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16776
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16776
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72278/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16776
**[Test build #72278 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72278/testReport)**
for PR 16776 at commit
[`db9ffc2`](https://github.com/apache/spark/commit/d
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16733
oh, sorry. I'll add the test soon.
---
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 a
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16733
@maropu are you able to add a simple test, in the style of other similar
tests? this looks like a fine fix.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/12135
@MLnick I created
SPARK-19436[https://issues.apache.org/jira/browse/SPARK-19436] for it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/12135
@gatorsmile it's a good point about the tests. However this JIRA & PR was
for exposing the multi-column functionality of `approxQuantiles`. The missing
test cases date back to original impl really. I
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16775
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16775
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72277/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16775
**[Test build #72277 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72277/testReport)**
for PR 16775 at commit
[`32c90dd`](https://github.com/apache/spark/commit/3
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16777
**[Test build #72280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72280/testReport)**
for PR 16777 at commit
[`bd0d9f7`](https://github.com/apache/spark/commit/bd
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16777
cc @hvanhovell, could you maybe take a look 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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16777#discussion_r99093765
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercionSuite.scala
---
@@ -53,7 +53,8 @@ class TypeCoercionSuite exten
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16777#discussion_r99093557
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercion.scala
---
@@ -101,24 +101,13 @@ object TypeCoercion {
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/16777
[SPARK-19435][SQL] Type coercion between ArrayTypes
## What changes were proposed in this pull request?
This PR proposes to support type coercion between `ArrayType`s where the
element
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16776
**[Test build #72279 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72279/testReport)**
for PR 16776 at commit
[`917fd6e`](https://github.com/apache/spark/commit/91
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16776
**[Test build #72278 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72278/testReport)**
for PR 16776 at commit
[`db9ffc2`](https://github.com/apache/spark/commit/db
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/16776
[SPARK-14352][FOLLOWUP][SQL] add tests for approxQuantile &
## What changes were proposed in this pull request?
1, check the behavior with illegal `quantiles` and `relativeError`
2, ad
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15797#discussion_r99075673
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -810,13 +825,43 @@ private[spark] class HiveExternalCatalog(co
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/12135#discussion_r99072952
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameStatFunctions.scala ---
@@ -75,13 +76,43 @@ final class DataFrameStatFunctions private[sql](d
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/14725
For future reference: Merged into 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
en
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/12135#discussion_r99071851
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameStatFunctions.scala ---
@@ -75,13 +76,43 @@ final class DataFrameStatFunctions private[sq
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16465
Merged into master & branch-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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16775
**[Test build #72277 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72277/testReport)**
for PR 16775 at commit
[`32c90dd`](https://github.com/apache/spark/commit/32
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16765
@gatorsmile Thanks for the review. I will update this soon.
---
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 viirya commented on the issue:
https://github.com/apache/spark/pull/16775
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 so, o
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/12135
Thanks for the reminder @gatorsmile (it wasn't in the list of things to do
when merging so I'll follow up and update the
http://spark.apache.org/committers.html docs to add that as a follow up step
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/12135#discussion_r99070440
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameStatFunctions.scala ---
@@ -75,13 +76,43 @@ final class DataFrameStatFunctions private[sql](d
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16765
The fix looks good to me. Just the comment about the test case. Thanks!
---
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 pro
201 - 300 of 304 matches
Mail list logo
