[ 
https://issues.apache.org/jira/browse/BIGTOP-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101462#comment-14101462
 ] 

Konstantin Boudnik edited comment on BIGTOP-1222 at 8/18/14 10:56 PM:
----------------------------------------------------------------------

Ok, I think we are getting somewhere. Jay has pointed out that I *need to be in 
bigtop-tests/bigtop-smoke-tests* directory to run the tests. I believe it is a 
better idea to be able to run the tests from the top-level directory. I am ok 
with solving it separately in a follow-up JIRA, but I believe this is a 
reasonable requirement to have.

Another point, when I am running pig smoke tests I see all sorts of mis-aligned 
Hadoop dependencies getting pulled in. E.g.
{noformat}
Download 
http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-hdfs/2.1.0-beta/hadoop-hdfs-2.1.0-beta.jar
Download 
http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-annotations/2.0.6-alpha/hadoop-annotations-2.0.6-alpha.jar
{noformat}
This is clearly caused by the mixed bag of deps. declared in the pig - and all 
others - smoke build.gradle


was (Author: cos):
Ok, I think we are getting somewhere. Jay has pointed out that I *need to be in 
bigtop-tests/bigtop-smoke-tests* directory to run the tests. I believe it is a 
better idea to be able to run the tests from the top-level directory. I am ok 
with solving it separately in a follow-up JIRA, but I believe this is a 
reasonable requirement to have.

Another point, when I am running pig smoke tests I see all sorts of mis-aligned 
Hadoop dependencies getting pulled in. E.g.
{noformat}
Download 
http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-hdfs/2.1.0-beta/hadoop-hdfs-2.1.0-beta.jar
Download 
http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-annotations/2.0.6-alpha/hadoop-annotations-2.0.6-alpha.jar
{noformat}
This is clearly cause by the mixed bag of deps. declared in the pig - and all 
others - smoke build.gradle

> Simplify and gradleize a subset of the bigtop smokes
> ----------------------------------------------------
>
>                 Key: BIGTOP-1222
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1222
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: build, tests
>    Affects Versions: 0.7.0
>            Reporter: jay vyas
>            Assignee: Konstantin Boudnik
>             Fix For: backlog
>
>         Attachments: BIGTOP-1222-2.patch, BIGTOP-1222.patch, 
> BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, 
> BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, 
> BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, 
> BIGTOP-1222.patch, BIGTOP-1222.patch, newsmokes.png
>
>
> (Rewritten the description for clarity)
> We need an easier way to run bigtop smoke tests, and gradle provides this:
> 1) Easy to script/modify
> 2) Human readable
> 3) equally oriented towards both groovy and plain old java
> The advantage of this method to running smokes : 
> 1) No need to compile a jar : this is a costly step and not much value added, 
> also creates indirection which can make debugging a broken test very hard.
> 2) Simple: A smoke test doesnt need to make low level API calls or be 
> compiled against the right APIs - rather, it should test the end user 
> interface ("hive -q  ....", "pig -x ....", "hadoop jar ....", and so on).  
> 3) Customizable:  The smoke tests shouldnt require users to have to write XML 
> and debug environmental variables / grep around for System properties etc.  
> Rather, a high level controller should do all that checking for you.  
> The initial idea was to write a python/bash implementation wrapper of 
> scripts, but that was replaced by the idea of using gradle.  The advantage of 
> gradle is that we don't need to manually set the classpath and run groovy 
> commands: Gradle wraps groovy scripts in their native java context quite 
> nicely - but it doesnt add any other unnecessary overhead (xml, jar files, no 
> need for complex xml tag wrappers for simple tasks - just plain groovy code).
> So, here the goal is just to create a nice, clean, extensible non-jar, 
> non-API dependent gradle runner for the smoke tests which exersizes the 
> hadoop cluster the same way a typical end-user would.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to