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/08/20 06:15:18 UTC

[jira] [Commented] (BIGTOP-1305) Use tests from the HBase test jar to potentially replace hbase-smokes

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

jay vyas commented on BIGTOP-1305:
----------------------------------

Hi [~apurtell] ........ BIGTOP-1222 is finally in.  would be great to see this patch extend it .  To do so

- add an hbase/ directory ith build.gradle file as is done in the other {{bigtop-tests/smoke-tests}} directory
- add hbase dependencies under the dependency markers, and so on.
- move or reference your existing hbase tests however you need to.  There are two ways to do this: 
   - You can see that, for example in mapreduce/, we actually reference the test-artifacts directory and just call them from the gradle fraamework
   - alternatively (i think better), you can *move* your hbase tests directory into the hbase/ directory you created under smoke-tests.  (i say better because i think the new framework is easier for folks to use, but theold framework is better from a jar building perspective, of course).


> Use tests from the HBase test jar to potentially replace hbase-smokes
> ---------------------------------------------------------------------
>
>                 Key: BIGTOP-1305
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1305
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Konstantin Boudnik
>            Assignee: Andrew Purtell
>             Fix For: backlog
>
>
> Andrew has suggested to use hbase provided tests instead of dealing with a separate set of hbase-smoke. I think this is a grand idea! We are doing something similar for Pig, hence we know it can be done.



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