[jira] [Commented] (HIVE-3314) Extract global limit configuration to optimizer
[ https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547992#comment-13547992 ] Hudson commented on HIVE-3314: -- Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/]) HIVE-3314 Extract global limit configuration to optimizer (Navis via namit) (Revision 1367405) Result = ABORTED namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1367405 Files : * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/GlobalLimitOptimizer.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/Optimizer.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/GlobalLimitCtx.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/ParseContext.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java Extract global limit configuration to optimizer --- Key: HIVE-3314 URL: https://issues.apache.org/jira/browse/HIVE-3314 Project: Hive Issue Type: Task Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Priority: Trivial Fix For: 0.10.0 Attachments: HIVE-3314.1.patch.txt SemanticAnalyzer is growing bigger and bigger. If some codes can be separated cleanly, it would be better to do that for simplicity. Was in part of HIVE-2925. Suggested to separate issue as https://issues.apache.org/jira/browse/HIVE-2925?focusedCommentId=13423754page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423754 -- 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-3314) Extract global limit configuration to optimizer
[ https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426031#comment-13426031 ] Carl Steinbach commented on HIVE-3314: -- @Namit: This ticket doesn't have a set fixversion, and more importantly the patch is not attached. Can you please fix this? Extract global limit configuration to optimizer --- Key: HIVE-3314 URL: https://issues.apache.org/jira/browse/HIVE-3314 Project: Hive Issue Type: Task Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Priority: Trivial SemanticAnalyzer is growing bigger and bigger. If some codes can be separated cleanly, it would be better to do that for simplicity. Was in part of HIVE-2925. Suggested to separate issue as https://issues.apache.org/jira/browse/HIVE-2925?focusedCommentId=13423754page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423754 -- 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-3314) Extract global limit configuration to optimizer
[ https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424711#comment-13424711 ] Namit Jain commented on HIVE-3314: -- +1 Extract global limit configuration to optimizer --- Key: HIVE-3314 URL: https://issues.apache.org/jira/browse/HIVE-3314 Project: Hive Issue Type: Task Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Priority: Trivial SemanticAnalyzer is growing bigger and bigger. If some codes can be separated cleanly, it would be better to do that for simplicity. Was in part of HIVE-2925. Suggested to separate issue as https://issues.apache.org/jira/browse/HIVE-2925?focusedCommentId=13423754page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423754 -- 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-3314) Extract global limit configuration to optimizer
[ https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424689#comment-13424689 ] Namit Jain commented on HIVE-3314: -- answered comments Extract global limit configuration to optimizer --- Key: HIVE-3314 URL: https://issues.apache.org/jira/browse/HIVE-3314 Project: Hive Issue Type: Task Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Priority: Trivial SemanticAnalyzer is growing bigger and bigger. If some codes can be separated cleanly, it would be better to do that for simplicity. Was in part of HIVE-2925. Suggested to separate issue as https://issues.apache.org/jira/browse/HIVE-2925?focusedCommentId=13423754page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423754 -- 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-3314) Extract global limit configuration to optimizer
[ https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424693#comment-13424693 ] Navis commented on HIVE-3314: - updated patch Extract global limit configuration to optimizer --- Key: HIVE-3314 URL: https://issues.apache.org/jira/browse/HIVE-3314 Project: Hive Issue Type: Task Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Priority: Trivial SemanticAnalyzer is growing bigger and bigger. If some codes can be separated cleanly, it would be better to do that for simplicity. Was in part of HIVE-2925. Suggested to separate issue as https://issues.apache.org/jira/browse/HIVE-2925?focusedCommentId=13423754page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423754 -- 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-3314) Extract global limit configuration to optimizer
[ https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424366#comment-13424366 ] Namit Jain commented on HIVE-3314: -- very minor comments on phabricator. Extract global limit configuration to optimizer --- Key: HIVE-3314 URL: https://issues.apache.org/jira/browse/HIVE-3314 Project: Hive Issue Type: Task Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Priority: Trivial SemanticAnalyzer is growing bigger and bigger. If some codes can be separated cleanly, it would be better to do that for simplicity. Was in part of HIVE-2925. Suggested to separate issue as https://issues.apache.org/jira/browse/HIVE-2925?focusedCommentId=13423754page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423754 -- 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
