Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16503#discussion_r95660339
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/OutputCommitCoordinator.scala ---
@@ -165,9 +167,14 @@ private[spark] class OutputCommitCoordinator(c
Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16503#discussion_r95659921
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/OutputCommitCoordinatorSuite.scala
---
@@ -221,6 +227,22 @@ private case class OutputCommitFunctions
Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16503#discussion_r95659396
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/OutputCommitCoordinatorSuite.scala
---
@@ -189,6 +188,13 @@ class OutputCommitCoordinatorSuite exten
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16404
I am fine to merge this at first.
---
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
enabl
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16404
Agree. Oracle behaves the same.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16558
Oops - 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 feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16550
**[Test build #71250 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71250/testReport)**
for PR 16550 at commit
[`beb4fd8`](https://github.com/apache/spark/commit/be
401 - 407 of 407 matches
Mail list logo