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

Edward Capriolo commented on HIVE-3127:
---------------------------------------

So I have found a reference to BlockMergeTask in 
./ql/src/java/org/apache/hadoop/hive/ql/exec/TaskFactory.java . 

Also the last release note was. ./build/dist/RELEASE_NOTES.txt:    * 
[HIVE-2413] - BlockMergeTask ignores client-specified jars

vi ./ql/src/java/org/apache/hadoop/hive/ql/io/rcfile/merge/BlockMergeTask.java

You could be correct in that the main is unreachable now. Maybe someone added 
it as a hack for direct testing, it would be good to cut-it from the code if it 
is not reachable. Maybe one of the other devs will chime in.

If not one else has any insight I will review and +1 tomorrow.

                
> Don’t pass–hconf values as command line arguments to child JVM to avoid 
> command line exceeding char limit on windows
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3127
>                 URL: https://issues.apache.org/jira/browse/HIVE-3127
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration, Windows
>    Affects Versions: 0.9.0, 0.10.0, 0.9.1
>            Reporter: Kanna Karanam
>            Assignee: Kanna Karanam
>              Labels: Windows
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3127.1.patch.txt, HIVE-3127.2.patch.txt, 
> HIVE-3127.3.patch.txt
>
>
> The maximum length of the DOS command string is 8191 characters (in Windows 
> latest versions http://support.microsoft.com/kb/830473). This limit will be 
> exceeded easily when it appends individual –hconf values to the command 
> string. To work around this problem, Write all changed hconf values to a temp 
> file and pass the temp file path to the child jvm to read and initialize the 
> -hconf parameters from file.

--
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


Reply via email to