Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214623731
**[Test build #56974 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56974/consoleFull)**
for PR 12686 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/12616#issuecomment-214622436
This is also supported by hadoop. For example, we can pass the globs in
sc.textFile("/dir/*/*"). I was wondering, if it will be implemented again.
---
If your
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12688#issuecomment-214622278
LGTM
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12685#issuecomment-214620448
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12688#issuecomment-214620464
cc @yhuai / @andrewor14
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12688#issuecomment-214620503
**[Test build #56973 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56973/consoleFull)**
for PR 12688 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12685#issuecomment-214620449
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/12688
[SPARK-14912][SQL] Propagate data source options to Hadoop configuration
## What changes were proposed in this pull request?
We currently have no way for users to propagate options to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12685#issuecomment-214620374
**[Test build #56967 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56967/consoleFull)**
for PR 12685 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/12685#issuecomment-214620302
LGTM pending Jenkins
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12687#issuecomment-214619924
**[Test build #56972 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56972/consoleFull)**
for PR 12687 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12520#issuecomment-214619179
**[Test build #2884 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2884/consoleFull)**
for PR 12520 at commit
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214619200
I see -- now I understand the motivation for returning the shuffle
dependencies topologically sorted, because it limits the depth of the recursion
(it looks like
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-214619175
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-214619176
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/12687
[SQL] Log native commands to find the number of tests that will be affected
if we do not delegate any statements to Hive
For Spark 2.0, Spark will handle all queries and statements. This PR aims
to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-214619052
**[Test build #56954 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56954/consoleFull)**
for PR 12629 at commit
Github user javawithjiva commented on the pull request:
https://github.com/apache/spark/pull/12520#issuecomment-214618915
Thank you for helping me get my first pull request out. Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12381#issuecomment-214618622
**[Test build #56971 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56971/consoleFull)**
for PR 12381 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214618462
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214618463
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214618451
**[Test build #56969 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56969/consoleFull)**
for PR 12686 at commit
Github user lw-lin commented on the pull request:
https://github.com/apache/spark/pull/12681#issuecomment-214617805
Some flaky tests not caused by this PR.
Jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214617772
@kayousterhout
I'll update the unit test and JIRA, PR descriptions to use the simpler
example.
As for the `createAncestorShuffleMapStages` way, I think it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214617649
**[Test build #56969 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56969/consoleFull)**
for PR 12686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12590#issuecomment-214617643
**[Test build #56970 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56970/consoleFull)**
for PR 12590 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12681#issuecomment-214617526
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12681#issuecomment-214617524
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12681#issuecomment-214617425
**[Test build #56953 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56953/consoleFull)**
for PR 12681 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214617100
**[Test build #56968 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56968/consoleFull)**
for PR 12421 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214616662
Rebased.
---
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 pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214616125
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214616123
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214616120
**[Test build #56966 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56966/consoleFull)**
for PR 12686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12686#issuecomment-214615986
**[Test build #56966 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56966/consoleFull)**
for PR 12686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12685#issuecomment-214615981
**[Test build #56967 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56967/consoleFull)**
for PR 12685 at commit
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/12686
[MINOR] Follow-up to #12625
## What changes were proposed in this pull request?
That patch mistakenly widened the visibility from `private[x]` to
`protected[x]`. This patch reverts
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214615564
Thank you! :)
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214615647
It works now! Thank you!
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214615366
**[Test build #56965 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56965/consoleFull)**
for PR 12268 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/12685
[SPARK-14313] [ML] [SparkR] AFTSurvivalRegression model persistence in
SparkR
## What changes were proposed in this pull request?
```AFTSurvivalRegressionModel``` supports ```save/load```
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214614924
Fixed in
https://github.com/apache/spark/commit/f8709218115f6c7aa4fb321865cdef8ceb443bd1
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214614851
**[Test build #56964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56964/consoleFull)**
for PR 12257 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214614770
@rxin It looks this is still failing,
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56962
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214613784
**[Test build #56963 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56963/consoleFull)**
for PR 12268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214613795
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214613897
OK pushed.
---
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 pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214613793
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214613611
Hah ok let me fix it for real.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12666#issuecomment-214613541
**[Test build #2883 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2883/consoleFull)**
for PR 12666 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214612978
It's a clean build after `git clean -fdx`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214612753
Ur, @rxin .
Could you check that again?
```
[error]
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214612442
**[Test build #56962 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56962/consoleFull)**
for PR 12257 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214612454
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214612460
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214611901
**[Test build #56963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56963/consoleFull)**
for PR 12268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214611834
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214611841
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214611632
**[Test build #56960 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56960/consoleFull)**
for PR 12684 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12666#issuecomment-214611155
LGTM pending Jenkins.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12666#issuecomment-214611080
**[Test build #2883 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2883/consoleFull)**
for PR 12666 at commit
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/1#discussion_r61027608
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveCommandSuite.scala
---
@@ -122,4 +134,105 @@ class HiveCommandSuite extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12668#issuecomment-214610321
@hvanhovell want 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 not have
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214609981
This was due to
https://github.com/apache/spark/commit/d2614eaadb93a48fba27fe7de64aff942e345f8e
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214609281
**[Test build #56962 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56962/consoleFull)**
for PR 12257 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214609252
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user lw-lin commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-214609215
some build issues unrelated to this PR.
Jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214609239
**[Test build #56961 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56961/consoleFull)**
for PR 12268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214609249
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12607#issuecomment-214609204
Hi @bomeng - thanks for doing this. I thought about it more and actually
think maybe it's not worth it to support these aliases, because it is going to
be confusing when
Github user dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/12684
---
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214609078
Sure! Thank for quick fix. I found that when I rebase my PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214608932
Thanks - actually I pushed directly to master just now. Can you close this?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12684#issuecomment-214608733
**[Test build #56960 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56960/consoleFull)**
for PR 12684 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214608734
**[Test build #56961 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56961/consoleFull)**
for PR 12268 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214608678
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/12684#issuecomment-214608530
cc @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 does not have this
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/12684
[HOTFIX][SQL] sparkSession can't be private.
## What changes were proposed in this pull request?
This fixes the following errors.
```
-@transient private val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214608176
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214608175
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214608169
**[Test build #56959 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56959/consoleFull)**
for PR 12268 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/12680#discussion_r61026788
--- Diff: mllib/src/main/scala/org/apache/spark/ml/r/KMeansWrapper.scala ---
@@ -17,14 +17,21 @@
package org.apache.spark.ml.r
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-214607771
**[Test build #56956 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56956/consoleFull)**
for PR 12641 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-214607778
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-21460
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214607350
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214607351
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214607346
**[Test build #56958 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56958/consoleFull)**
for PR 12257 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-214607395
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-214607393
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-214607369
**[Test build #56959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56959/consoleFull)**
for PR 12268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12683#issuecomment-214607333
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-214607377
**[Test build #56957 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56957/consoleFull)**
for PR 12638 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12679#issuecomment-214607013
@hvanhovell @yhuai Could you review the changes? Thank you!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user lw-lin commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-214606875
@marmbrus thanks for the patient reminder!
Since I've reverted the renaming, and I've checked there's no other
completely unused class under
GitHub user GayathriMurali opened a pull request:
https://github.com/apache/spark/pull/12683
[SPARK-14315][SparkR]Add model persistence to GLMs
## What changes were proposed in this pull request?
Add model persistence to GLMs in SparkR
Unit tests added
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-214606828
**[Test build #56956 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56956/consoleFull)**
for PR 12641 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-214606829
**[Test build #56957 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56957/consoleFull)**
for PR 12638 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-214606825
**[Test build #56958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56958/consoleFull)**
for PR 12257 at commit
GitHub user lw-lin reopened a pull request:
https://github.com/apache/spark/pull/12638
[SPARK-14874][SQL][Streaming] Remove the obsolete Batch representation
## What changes were proposed in this pull request?
The `Batch` class, which had been used to indicate progress in a
1 - 100 of 786 matches
Mail list logo
