Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
thanks for the reviews @cloud-fan
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18162
thanks, merging 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78468/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78468 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78468/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
Jenkins, test 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78460/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78460 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78460/testReport)**
for PR 18162 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78468 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78468/testReport)**
for PR 18162 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78467/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
**[Test build #78467 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78467/testReport)**
for PR 18162 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78467 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78467/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
Jenkins, test 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
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
failure is from previous push of code.
---
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/18162
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/18162
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78466/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78466 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78466/testReport)**
for PR 18162 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78466 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78466/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
upmerged to master and updated default and removed unneeded changes.
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
will upmerge shortly, since there are conflicts
---
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 issue:
https://github.com/apache/spark/pull/18162
**[Test build #78460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78460/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
sorry missed that you had commented, yes we can change that
---
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
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18162
@tgravescs can you address
https://github.com/apache/spark/pull/18162#discussion_r122363701 ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78300/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
**[Test build #78300 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78300/testReport)**
for PR 18162 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #78300 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78300/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
Jenkins, test 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
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
sorry been out on vacation and probably won't have time this week to
respond much but will update early next week. Thanks @rdblue . I am running
this in our production as well and can clearly
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/18162
@tgravescs, I deployed this to our production environment (based on 2.0.0)
a few days ago and haven't hit any problems with it. I think this is good to
go, unless something has been added recently
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77687/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
**[Test build #77687 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77687/testReport)**
for PR 18162 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77684/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
**[Test build #77684 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77684/testReport)**
for PR 18162 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #77687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77687/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
I'm not sure what you mean by its not doable? what places are you seeing
update the block statuses that I haven't covered here? most of it was done by
the BlockManager. Maybe I'm missing
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18162
I'm wondering if it's doable to stop tracking the `updatedBlockStatus`
according to a config... there are many places that update `updatedBlockStatus`
right?
---
If your project is set up for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #77684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77684/testReport)**
for PR 18162 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
**[Test build #77682 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77682/testReport)**
for PR 18162 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77682/
Test FAILed.
---
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
turned on by default for backwards compatibility but don't really agree
with it. We should make it more stable/usable for people by turning it off.
I'm assuming anyone that is using this would
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #77682 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77682/testReport)**
for PR 18162 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
ok, I'll update the default.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18162
Yea I think we should merge this to 2.2, but we need to change the default
value of the new config to `true`, to not surprise users.
---
If your project is set up for it, you can reply to this
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
@JoshRosen what do you think should we add the deprecated?
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
It would be nice to get this into spark 2.2 if we can
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/18162
Yeah I was figuring I would file another jira to remove it later. I can
add the deprecated flag here if you guys agree.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18162
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/18162
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77625/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #77625 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77625/testReport)**
for PR 18162 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18162
I do love the clean up you did by removing `updatedBlockStatuses`
entirely... Since `SparkListenerTaskEnd` is marked as a developer API, is it
acceptable to make
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18162
**[Test build #77625 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77625/testReport)**
for PR 18162 at commit
57 matches
Mail list logo
