[
https://issues.apache.org/jira/browse/HIVE-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kanna Karanam updated HIVE-3126:
--------------------------------
Attachment: HIVE-3126.4.patch.txt
Thanks Carl. This feedback helped me to move the path conversion/escaping logic
from .vm files to QTestGen task. It is a code generation logic so to even
create a file object, we need to get the absolute path in a string format so we
can’t skip the escaping logic. Here is the generated code line. (new
File("D:\\OSS\\Hive\\ql\\src\\test\\queries\\clientpositive\\input37.q");
File, Path, & URI objects are helping us to work across Windows & Unix
operating systems with no explicit conversions. But when it comes to Hadoop,
JAVA can’t convert the URIs between “local file system” vs “hdfs”. URIs in Unix
& HDFS are more or less same format and the paths in Unix don’t contain “:”
character so we don’t notice this problem. In windows, because of the”:” Hadoop
treats the windows drive letter as file scheme so we need to remove it to avoid
this problem.
Thanks
> Generate & build the velocity based Hive tests on windows by fixing the path
> issues
> -----------------------------------------------------------------------------------
>
> Key: HIVE-3126
> URL: https://issues.apache.org/jira/browse/HIVE-3126
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.9.0, 0.10.0, 0.9.1
> Reporter: Kanna Karanam
> Assignee: Kanna Karanam
> Labels: Windows, test
> Fix For: 0.10.0
>
> Attachments: HIVE-3126.1.patch.txt, HIVE-3126.2.patch.txt,
> HIVE-3126.3.patch.txt, HIVE-3126.4.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 from
--
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
