Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/374#issuecomment-40229263
Okay, that's a good point. Why don't you just move the before and after
functions that turn on caching into hive compatibility and remove the in
memory sub class.
On Apr 11, 2014 10:18 AM, "Cheng Lian" <[email protected]> wrote:
> @marmbrus <https://github.com/marmbrus> I think we'd better remove either
> HiveInMemoryCompatabilitySuite or HiveCompatabilitySuite. Travis
> complains that the build time is too long (> 50 min). I prefer removing
> HiveCompatabilitySuite since the in-memory version should have already
> covered it.
>
> --
> Reply to this email directly or view it on
GitHub<https://github.com/apache/spark/pull/374#issuecomment-40227452>
> .
>
---
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 feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
