[jira] [Commented] (HIVE-2913) BlockMergeTask Doesn't Honor Job Configuration Properties when used directly
[ https://issues.apache.org/jira/browse/HIVE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13548050#comment-13548050 ] Hudson commented on HIVE-2913: -- Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/]) HIVE-2913. Fixes BlockMergeTask to honor Configuration Properties when used directly. (Thiruvel Thirumoolan via amareshwari) (Revision 1308812) Result = ABORTED amareshwari : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1308812 Files : * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/io/rcfile/merge/BlockMergeTask.java BlockMergeTask Doesn't Honor Job Configuration Properties when used directly Key: HIVE-2913 URL: https://issues.apache.org/jira/browse/HIVE-2913 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.8.1 Reporter: Thiruvel Thirumoolan Assignee: Thiruvel Thirumoolan Priority: Minor Fix For: 0.9.0 Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2913.D2547.1.patch, blockmerge.sh, HIVE-2913_1.patch BlockMergeTask has a main() and when used directly (instead of say partition concatenate feature), the -jobconf arguments are not honored. This is not something most people directly use. Usage: BlockMergeTask -input colon seperated input paths -outputDir outputDir [-jobconf k1=v1 [-jobconf k2=v2] ...] To reproduce: Run BlockMergeTask with say -jobconf mapred.job.name=test and launched job will have a different name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2913) BlockMergeTask Doesn't Honor Job Configuration Properties when used directly
[ https://issues.apache.org/jira/browse/HIVE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245592#comment-13245592 ] Hudson commented on HIVE-2913: -- Integrated in Hive-trunk-h0.21 #1350 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1350/]) HIVE-2913. Fixes BlockMergeTask to honor Configuration Properties when used directly. (Thiruvel Thirumoolan via amareshwari) (Revision 1308812) Result = FAILURE amareshwari : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1308812 Files : * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/io/rcfile/merge/BlockMergeTask.java BlockMergeTask Doesn't Honor Job Configuration Properties when used directly Key: HIVE-2913 URL: https://issues.apache.org/jira/browse/HIVE-2913 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.8.1 Reporter: Thiruvel Thirumoolan Assignee: Thiruvel Thirumoolan Priority: Minor Fix For: 0.9.0 Attachments: HIVE-2913.D2547.1.patch, HIVE-2913_1.patch, blockmerge.sh BlockMergeTask has a main() and when used directly (instead of say partition concatenate feature), the -jobconf arguments are not honored. This is not something most people directly use. Usage: BlockMergeTask -input colon seperated input paths -outputDir outputDir [-jobconf k1=v1 [-jobconf k2=v2] ...] To reproduce: Run BlockMergeTask with say -jobconf mapred.job.name=test and launched job will have a different name. -- 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
[jira] [Commented] (HIVE-2913) BlockMergeTask Doesn't Honor Job Configuration Properties when used directly
[ https://issues.apache.org/jira/browse/HIVE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244971#comment-13244971 ] Amareshwari Sriramadasu commented on HIVE-2913: --- +1. Running tests. Will commit once tests pass. BlockMergeTask Doesn't Honor Job Configuration Properties when used directly Key: HIVE-2913 URL: https://issues.apache.org/jira/browse/HIVE-2913 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.8.1 Reporter: Thiruvel Thirumoolan Assignee: Thiruvel Thirumoolan Priority: Minor Fix For: 0.9.0 Attachments: HIVE-2913.D2547.1.patch, HIVE-2913_1.patch, blockmerge.sh BlockMergeTask has a main() and when used directly (instead of say partition concatenate feature), the -jobconf arguments are not honored. This is not something most people directly use. Usage: BlockMergeTask -input colon seperated input paths -outputDir outputDir [-jobconf k1=v1 [-jobconf k2=v2] ...] To reproduce: Run BlockMergeTask with say -jobconf mapred.job.name=test and launched job will have a different name. -- 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
[jira] [Commented] (HIVE-2913) BlockMergeTask Doesn't Honor Job Configuration Properties when used directly
[ https://issues.apache.org/jira/browse/HIVE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244973#comment-13244973 ] Phabricator commented on HIVE-2913: --- amareshwarisr has accepted the revision HIVE-2913 [jira] BlockMergeTask Doesn't Honor Job Configuration Properties when used directly. +1 REVISION DETAIL https://reviews.facebook.net/D2547 BRANCH svn BlockMergeTask Doesn't Honor Job Configuration Properties when used directly Key: HIVE-2913 URL: https://issues.apache.org/jira/browse/HIVE-2913 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.8.1 Reporter: Thiruvel Thirumoolan Assignee: Thiruvel Thirumoolan Priority: Minor Fix For: 0.9.0 Attachments: HIVE-2913.D2547.1.patch, HIVE-2913_1.patch, blockmerge.sh BlockMergeTask has a main() and when used directly (instead of say partition concatenate feature), the -jobconf arguments are not honored. This is not something most people directly use. Usage: BlockMergeTask -input colon seperated input paths -outputDir outputDir [-jobconf k1=v1 [-jobconf k2=v2] ...] To reproduce: Run BlockMergeTask with say -jobconf mapred.job.name=test and launched job will have a different name. -- 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
