[
https://issues.apache.org/jira/browse/HCATALOG-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486130#comment-13486130
]
Travis Crawford commented on HCATALOG-535:
------------------------------------------
What's the reason for wanting to require e2e tests run against a "real
cluster"? Pseudo-distributed mode exercises all the components talking to each
other over the network, which are the same code-paths a fully distributed
cluster uses. Its not practical to assume everyone who wants to submit a patch
has this infrastructure setup. If we had a tester that launched on ec2 or some
other public cloud that would be reasonable, but penalizing people for not
having a mirror of Yahoo's internal infrastructure seems like something we want
to avoid.
For the Apache project, I think having a baseline test that anyone can run on a
single machine is totally appropriate. If committers see a patch and think "hey
I'd like to run this through our internal integration tests before committing"
that seems totally appropriate to ask for.
> HCatalog e2e tests should run locally with minimal configuration
> ----------------------------------------------------------------
>
> Key: HCATALOG-535
> URL: https://issues.apache.org/jira/browse/HCATALOG-535
> Project: HCatalog
> Issue Type: Improvement
> Reporter: Travis Crawford
> Assignee: Travis Crawford
>
> Setting up the environment to run e2e tests is documented here:
> https://cwiki.apache.org/confluence/display/HCATALOG/How+To+Test
> Its extremely time consuming to setup because there are so many moving parts.
> Some are very machine-specific, like configuring SSH and installing MySQL for
> your platform. However, some stuff we can automate for the developer, like
> downloading, installing & configuring all the Java stuff. We should do that
> to simplify.
> Also, tests do not run from a git repo because of the svn external. This
> would be very helpful to fix. Developing with Git is WAAAAAY nicer because
> branching is so easy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
