[jira] [Commented] (HIVE-5666) use Path instead of String for IOContext.inputPath

["Hive QA (JIRA)" <ji...@apache.org>]

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

Hive QA commented on HIVE-5666:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12610514/HIVE-5666.1.patch

{color:green}SUCCESS:{color} +1 4502 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1267/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1267/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

> use Path instead of String for IOContext.inputPath
> --------------------------------------------------
>
>                 Key: HIVE-5666
>                 URL: https://issues.apache.org/jira/browse/HIVE-5666
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-5666.1.patch
>
>
> Path is converted to string in HiveContextAwareRecordReader to be stored in IOContext.inputPath, then in MapOperator normalizePath gets called on it which converts it back to Path. 
> Path creation is expensive, so it is better to use Path instead of string through the call stack.
> This is also a step towards HIVE-3616.



--
This message was sent by Atlassian JIRA
(v6.1#6144)