Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13686
**[Test build #3108 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3108/consoleFull)**
for PR 13686 at commit
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/13686
I'm going to close this PR and open a new one when I've fixed the test
failures. My bad.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/13686
Aaaak! Some unit tests are failing on my build. Sorry, I will re-examine
and submit a new commit. Ugh.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/13686
Actually, let me think about this some more...
---
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 mallman commented on the issue:
https://github.com/apache/spark/pull/13686
@hvanhovell Sounds like a good idea, but I don't know how to unit test this
without opening up some of this caching api to at least the `private[hive]`
access level. Would that be acceptable? I'm
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/13686
@mallman could you add a unit test for this?
---
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/13686
**[Test build #3108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3108/consoleFull)**
for PR 13686 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13686
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 project does not have this
