[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #69013 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69013/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user andrewor14 commented on the issue: https://github.com/apache/spark/pull/15896 I personally think `UNCACHE TABLE IF EXISTS` is best. It preserves the old behavior but lets the user make sure a table is not cached if they really want. --- If your project is set up for it,

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user dongjoon-hyun commented on the issue: https://github.com/apache/spark/pull/15896 I see. Thank you for informing that, @brkyvz --- 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user brkyvz commented on the issue: https://github.com/apache/spark/pull/15896 On hold on my side. Will try to get back to it On Nov 17, 2016 3:31 PM, "Dongjoon Hyun" wrote: > Hi, @brkyvz and @gatorsmile

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user dongjoon-hyun commented on the issue: https://github.com/apache/spark/pull/15896 Hi, @brkyvz and @gatorsmile . Does this proceed to Option 1 or 2 for now? Or is this holding on for next month? --- If your project is set up for it, you can reply to this email and have

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user gatorsmile commented on the issue: https://github.com/apache/spark/pull/15896 @brkyvz Why not supporting both? : ) --- 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user brkyvz commented on the issue: https://github.com/apache/spark/pull/15896 @gatorsmile Talking offline with several people, I may put this PR on hold for now since it is a behavior change. I guess it would be better to go with Options 1 or 2 that I defined in the PR

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68730/ Test PASSed. ---

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68730 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68730/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68730 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68730/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68726/ Test FAILed. ---

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68726 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68726/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68726 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68726/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68725/ Test FAILed. ---

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68725 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68725/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68725 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68725/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user gatorsmile commented on the issue: https://github.com/apache/spark/pull/15896 After fixed the styles, LGTM pending testing. --- 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68685 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68685/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68685/ Test FAILed. ---

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68685 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68685/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 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] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68684 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68684/consoleFull)** for PR 15896 at commit

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user brkyvz commented on the issue: https://github.com/apache/spark/pull/15896 cc @gatorsmile I changed a test you added. Do you have any strong feelings on this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/15896 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68684/ Test FAILed. ---

[GitHub] spark issue #15896: [SPARK-18465] Uncache table shouldn't throw an exception...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/15896 **[Test build #68684 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68684/consoleFull)** for PR 15896 at commit