[
https://issues.apache.org/jira/browse/HIVE-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402850#comment-13402850
]
Kanna Karanam commented on HIVE-3204:
-------------------------------------
WOW.. Thanks Edward. You simplified the problem very quickly. I will start with
this approach. I noticed that our unit tests are using “!rm, !ls, !mkdir,
!sleep” shell commands as of today. So I can easily replace all of them using
either DFS or java_method. But I am worried that it leaves me with no unit
testing for “!<cmd> command.
I can workaround this by adding a platform specific unit tests to test this
command (one for windows and another one for Unix). Do you have any suggestions?
Thanks
> Windows: Fix the unit tests which contains “!<cmd>” commands (Unix shell
> commands)
> ----------------------------------------------------------------------------------
>
> Key: HIVE-3204
> URL: https://issues.apache.org/jira/browse/HIVE-3204
> Project: Hive
> Issue Type: Sub-task
> Components: Tests, Windows
> Affects Versions: 0.10.0
> Reporter: Kanna Karanam
> Assignee: Kanna Karanam
> Fix For: 0.10.0
>
>
> Possible solution 1: (Preferred one)
> !<Unix cmd | Windows cmd> => Keeping the same syntax. Hive uses Java runtime
> to launch the shell command so any attempt to run windows commands on Unix
> will fail and vice versa.
> To deal with unit tests. Unix commands in each .q file will be modified as
> shown below. I will filter out the !commands which can’t be run on the
> current .
> Original entry in.q file:
> !rm -rf ../build/ql/test/data/exports/exim_department;
> It will be replaced with the following entries.
> UNIX::!rm -rf ../build/ql/test/data/exports/exim_department;
> WINDOWS::!del ../build/ql/test/data/exports/exim_department
> Possible solution 2:
> Provide a Shell UDF library(JAVA Based code)to support platform independent
> shell functionality
> Cons –
> 1) Difficult to provide full shell functionality
> 2) Takes long time
> 3) Difficult to manage
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
