You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/03/21 19:47:43 UTC
[jira] [Comment Edited] (BIGTOP-1222) Completely gradleize the
bigtop smokes
[ https://issues.apache.org/jira/browse/BIGTOP-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943372#comment-13943372 ]
jay vyas edited comment on BIGTOP-1222 at 3/21/14 6:46 PM:
-----------------------------------------------------------
(rehashing my above question: still need a wiki page or something about this)
I still dont understand fully why, for smoke tests, we care about maven dependencies at all? To me, they are just a means to an end (we need ITest on the classpath to run hadoop commands and leverage the awesome bigtop smoke tests , so we go ahead and find a way to add it - but we dont care much about having the exact right version of it)....
Smoke tests should test the command line hadoop invocations like
{noformat}
hadoop fs -ls
hbase shell -d create 't1','f1'
pig -x ....
{noformat}
These should gather their runtime info from /usr/lib/hadoop/lib, /urs/pig/lib, etc.
Regarding carrots to potatoes: The end user's invocation of a hadoop command which delivers them some real insight into their big data problem space is the "real potatoes" that the smoke tests should be testing. Right?
was (Author: jayunit100):
(rehashing my above question: still need a wiki page or something about this)
I still dont understand fully why, for smoke tests, we care about maven dependencies at all?
Smoke tests should test the command line hadoop invocations like
{noformat}
hadoop fs -ls
hbase shell -d create 't1','f1'
pig -x ....
{noformat}
These should gather their runtime info from /usr/lib/hadoop/lib, /urs/pig/lib, etc.
Regarding carrots to potatoes: The end user's invocation of a hadoop command which delivers them some real insight into their big data problem space is the "real potatoes" that the smoke tests should be testing. Right?
> Completely gradleize the bigtop smokes
> --------------------------------------
>
> Key: BIGTOP-1222
> URL: https://issues.apache.org/jira/browse/BIGTOP-1222
> Project: Bigtop
> Issue Type: Improvement
> Components: Build
> Affects Versions: 0.7.0
> Reporter: jay vyas
>
> Currently, there is a JIRA underway to make running the maven based smoke tests easier: BIGTOP-1195.
> Eventually, however, maybe we could run these smokes from gradle. I think that will obviate BIGTOP-1195 (Although i still assert a bash driver is a big win/gain for bigtop's goals : which are to unify the hadoop packaging and deployment paradigm).
> - run the smokes using a simple gradle goal
> - smokes should be easily runnable as scripts, with no need for jar file intermediates.
> - The bash driver for BIGTOP-1195 (if accepted, still under debate) should be upgraded to use the new gradle smokes
> - Delete old maven smokes.
> This might be a little ambitious, if so others chime in. I'm not a gradle/groovy expert but getting more well versed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)