[
https://issues.apache.org/jira/browse/BIGTOP-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063001#comment-14063001
]
jay vyas edited comment on BIGTOP-1222 at 7/16/14 2:08 AM:
-----------------------------------------------------------
build.gradle expects all the usual suspects ( PIG_HOME,HADOOP_CONF_DIR and so
on) to be declared, or it wont run.
I can probably make it a little smarter, so that it only requires PIG_HOME if
indeed pig tests are being run, and so on.
[~dawson.choong] are you interested in helping me on the patch? That would be
awesome ! Im busy right now again, and wont be able to finish this patch
until later in the week,but if your ready - Maybe you can pull the patch down,
add a few extensions to it, and create a second patch of your own. Then to
complete the JIRA, we can just commit both patches at once in the proper order.
was (Author: jayunit100):
build.gradle expects all the usual suspects ( PIG_HOME,HADOOP_CONF_DIR and so
on) to be declared, or it wont run.
I can probably make it a little smarter, so that it only requires PIG_HOME if
indeed pig tests are being run, and so on.
Dawson are you interested in helping me on the patch? That would be awesome !
Im busy right now again, and wont be able to finish this patch until later in
the week,but if your ready - Maybe you can pull the patch down, add a few
extensions to it, and create a second patch of your own. Then to complete the
JIRA, we can just commit both patches at once in the proper order.
> 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: jay vyas
> Fix For: backlog
>
> Attachments: BIGTOP-1222-2.patch, BIGTOP-1222.patch,
> BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch, BIGTOP-1222.patch
>
>
> (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)
