You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "He Yongqiang (JIRA)" <ji...@apache.org> on 2011/04/22 21:07:05 UTC
[jira] [Created] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Hive's symlink text input format should be able to work with ComineHiveInputFormat
----------------------------------------------------------------------------------
Key: HIVE-2126
URL: https://issues.apache.org/jira/browse/HIVE-2126
Project: Hive
Issue Type: Improvement
Reporter: He Yongqiang
Assignee: He Yongqiang
at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
The reason we are doing it at compile time is because:
1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024891#comment-13024891 ]
Namit Jain commented on HIVE-2126:
----------------------------------
It might be simpler if the HiveInputFormat (or a new interface which extends InputFommat) adds
this new method.
All Hive input formats will implement the above interface. The default implementation does nothing,
You dont need code like below:
if (partDesc.getInputFileFormatClass().equals(SymlinkTextInputFormat.class)) {
//change to TextInputFormat
You always call a new method, which is a no-op for all other input formats right now.
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024883#comment-13024883 ]
He Yongqiang commented on HIVE-2126:
------------------------------------
The reason of using"ReworkMapredInputFormat" is that the interface "reworkMapred" can also be used by other formats in future, like some other file format also want to change the mapred work depends on the input.
what do you think?
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Yongqiang updated HIVE-2126:
-------------------------------
Attachment: HIVE-2126.2.patch
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch, HIVE-2126.2.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024956#comment-13024956 ]
Namit Jain commented on HIVE-2126:
----------------------------------
can you update the review board ?
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch, HIVE-2126.2.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Yongqiang updated HIVE-2126:
-------------------------------
Status: Patch Available (was: Open)
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024840#comment-13024840 ]
Namit Jain commented on HIVE-2126:
----------------------------------
I havent taken a look at the code - but a high level question.
Should we call it SymbolicInputFormat instead ?
I mean, it should work for all kinds of files - not just text files.
For backward compatibility, we can make SymbolicTextInputFormat extend
SymbolicInputFormat.
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024761#comment-13024761 ]
jiraposter@reviews.apache.org commented on HIVE-2126:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/653/
-----------------------------------------------------------
Review request for hive.
Summary
-------
Hive's symlink text input format should be able to work with ComineHiveInputFormat
This addresses bug hive-2126.
https://issues.apache.org/jira/browse/hive-2126
Diffs
-----
trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java 1096093
trunk/conf/hive-default.xml 1096093
trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 1096093
trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/Task.java 1096093
trunk/ql/src/java/org/apache/hadoop/hive/ql/io/ReworkMapredInputFormat.java PRE-CREATION
trunk/ql/src/java/org/apache/hadoop/hive/ql/io/SymlinkTextInputFormat.java 1096093
trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/ExplainSemanticAnalyzer.java 1096093
trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 1096093
trunk/ql/src/test/org/apache/hadoop/hive/ql/io/TestSymlinkTextInputFormat.java 1096093
Diff: https://reviews.apache.org/r/653/diff
Testing
-------
Thanks,
Yongqiang
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2126:
---------------------------------
Fix Version/s: 0.8.0
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Fix For: 0.8.0
>
> Attachments: HIVE-2126.1.patch, HIVE-2126.2.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025076#comment-13025076 ]
Namit Jain commented on HIVE-2126:
----------------------------------
+1
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch, HIVE-2126.2.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024760#comment-13024760 ]
He Yongqiang commented on HIVE-2126:
------------------------------------
review board: https://reviews.apache.org/r/653/
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Yongqiang updated HIVE-2126:
-------------------------------
Attachment: HIVE-2126.1.patch
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-2126:
-----------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed. Thanks Yongqiang
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch, HIVE-2126.2.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2126) Hive's symlink text input format
should be able to work with ComineHiveInputFormat
Posted by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024957#comment-13024957 ]
jiraposter@reviews.apache.org commented on HIVE-2126:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/653/
-----------------------------------------------------------
(Updated 2011-04-25 20:48:09.176419)
Review request for hive.
Changes
-------
added a new class SymbolicInputFormat, and move the reworkMapred to this new class.
move the new code from SemanticAnalyzer to a Utilities method
Summary
-------
Hive's symlink text input format should be able to work with ComineHiveInputFormat
This addresses bug hive-2126.
https://issues.apache.org/jira/browse/hive-2126
Diffs (updated)
-----
trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java 1096548
trunk/conf/hive-default.xml 1096548
trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 1096548
trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/Task.java 1096548
trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java 1096548
trunk/ql/src/java/org/apache/hadoop/hive/ql/io/ReworkMapredInputFormat.java PRE-CREATION
trunk/ql/src/java/org/apache/hadoop/hive/ql/io/SymbolicInputFormat.java PRE-CREATION
trunk/ql/src/java/org/apache/hadoop/hive/ql/io/SymlinkTextInputFormat.java 1096548
trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/ExplainSemanticAnalyzer.java 1096548
trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 1096548
trunk/ql/src/test/org/apache/hadoop/hive/ql/io/TestSymlinkTextInputFormat.java 1096548
Diff: https://reviews.apache.org/r/653/diff
Testing
-------
Thanks,
Yongqiang
> Hive's symlink text input format should be able to work with ComineHiveInputFormat
> ----------------------------------------------------------------------------------
>
> Key: HIVE-2126
> URL: https://issues.apache.org/jira/browse/HIVE-2126
> Project: Hive
> Issue Type: Improvement
> Reporter: He Yongqiang
> Assignee: He Yongqiang
> Attachments: HIVE-2126.1.patch, HIVE-2126.2.patch
>
>
> at compile time, if a partition's file format is SymlinkTextInputFormat, will replace the symlink path with paths in the symlink file. This way, it will work with Hive's HiveCombineFileInputFormat.
> The reason we are doing it at compile time is because:
> 1) At run time, the input path is not only used to get record reader, but also used for hive to get aliases and thus operator tree. But the CombineHiveInputFormat can have multiple paths for each split, and when switching paths, it also set the job with new input file name. So it always require a real input path name. Can not fake it.
> 2) if write a new input format, it will require a lot of duplication work with existing CombineHiveInputFormat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira