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

Zoltan Haindrich commented on HIVE-14415:
-----------------------------------------

[~pvary]  I'm not actively working on those other things...i've experimented 
with cli execution from eclipse about a month ago..and those are some minor 
issues I identified..

wow!...i wasn't aware that beeline tests are also disabled...there are about 20 
cli tests...testaccumuloclidriver is also disabled - but i was unable to 
determine how HIVE-14391 ;)

I think an umbrella jira ticket would be useful....i've created HIVE-14443 

i've started working on migrating the other clidrivers one-by-one...I haven't 
reached beeline yet...so just submit it as a new ticket; or if you send me a 
pastebin link i'll add it to the second patch

cheers! :)

> Upgrade qtest execution framework to junit4 - TestPerfCliDriver
> ---------------------------------------------------------------
>
>                 Key: HIVE-14415
>                 URL: https://issues.apache.org/jira/browse/HIVE-14415
>             Project: Hive
>          Issue Type: Improvement
>          Components: Tests
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>         Attachments: HIVE-14415.1.patch, HIVE-14415.2.patch
>
>
> I would like to upgrade the current maven+ant+velocimacro+junit4 qtest 
> generation&execution framework to use only junit4 - while (trying) to keep 
> all the existing features it provides.
> What I can't really do with the current one: execute easily a single qtests 
> from an IDE (as a matter of fact I can...but it's way too complicated; after 
> this it won't be a cake-walk either...but it will be a step closer ;)
> I think this change will make it more clear how these tests are configured 
> and executed.
> I will do this in two phases, currently i will only change 
> {{TestPerfCliDriver}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to