Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14152
I'm gonna go for this if there are no objections. I'd even put it into 2.0,
but unless someone seconds that I won't.
---
If your project is set up for it, you can reply to this email and have your
r
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14152
@tdas how does the substance of the change strike you? it's an improvement
over the current situation where millions of checkpoints would stack up, but
the cap of 1000 was arbitrary. I didn't necessa
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14152
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62164/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14152
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/14152
**[Test build #62164 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62164/consoleFull)**
for PR 14152 at commit
[`a6fce66`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14152
**[Test build #62164 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62164/consoleFull)**
for PR 14152 at commit
[`a6fce66`](https://github.com/apache/spark/commit/a
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14152
CC @tdas
---
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 f
