hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanna Karanam (JIRA)" <>
Subject [jira] [Commented] (HIVE-3126) Generate & build the velocity based Hive tests on windows by fixing the path issues
Date Mon, 18 Jun 2012 03:58:43 GMT


Kanna Karanam commented on HIVE-3126:

Hi Edward – It is a good point. Hive development on Windows is not ready yet, still around
20% of unit tests are failing. So I am working on addressing them in subsequent JIRAs (Sub
tasks of this JIRA & not created them yet). This Patch will enable other developers to
build and fix any of the existing UT failures on Windows.  Here is my plan to get the Windows
development environment ready.

1) This JIRA addresses to generate and build the velocity based unit tests on Windows.
2) I will be creating bunch of JIRAs to address the UT failures on Windows (It completes the
work to run all UTs generated on Linux to work on Windows)
3) Enable the Hive development on Windows . it will address UTs developed on Windows to work
on Linux too.
Please let me know if I missed anything.


> Generate & build the velocity based Hive tests on windows by fixing the path issues
> -----------------------------------------------------------------------------------
>                 Key: HIVE-3126
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.9.0, 0.10.0, 0.9.1
>            Reporter: Kanna Karanam
>              Labels: Windows, test
>             Fix For: 0.10.0
>         Attachments: HIVE-3126.1.patch.txt
> 1)Escape the backward slash in Canonical Path if unit test runs on windows.
> 2)Diff comparison – 
>      a.	Ignore the extra spacing on windows
>      b.	Ignore the different line endings on windows & Unix
>      c.	Convert the file paths to windows specific. (Handle spaces etc..)
> 3)Set the right file scheme & class path separators while invoking the junit task

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message