Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Bigtop >> mail # user >> Re: The combinatorial problem of testing hadoop ecosystem tools

Copy link to this message
Re: The combinatorial problem of testing hadoop ecosystem tools
Mean to include a link: https://issues.apache.org/jira/browse/BIGTOP-848

On Mon, Jun 10, 2013 at 11:20 AM, Sean Mackrory <[EMAIL PROTECTED]>wrote:

> Hi Jay,
> Welcome to the community! You may be interested in the JIRA BIGTOP-848.
> One of the purposes of that effort is to make it possible to build and
> package "trunk" from the upstream projects, so that integration issues can
> be found without having to wait for a release. Being able to build from an
> arbitrary commit would also be a step towards what you are describing, but
> only if the project has not changed dramatically from the version currently
> supported by Bigtop. Trying to build Hadoop 1.x.x with the current 2.0.x
> packaging code, for example, would not work at all - and it would require
> substantial work to make the packaging code so backwards compatible.
> On Mon, Jun 10, 2013 at 11:10 AM, Jay Vyas <[EMAIL PROTECTED]> wrote:
>> Hi again big top !
>> It would be nice if one could to specify certain distribution components
>> (for example, hbase 0.94.7, with hadoop 1.x.x , etc...) in my BigTop
>> deployments to test matrices of interoperable components).
>> As we all know, its common for different people to run different versions
>> of ecosystem components without integrating them.  For example, maybe
>> someone will have an old version of HIVE running on a new
>> Is this commonly done or has anyone worked on the combinatorial ecosystem
>> match up testing problem in BigTop ?  It seems like it might be tricky to
>> select and deal with the fact that ecosystem tools are constantly being
>> upgraded at different rates.
>> --
>> Jay Vyas
>> http://jayunit100.blogspot.com