[
https://issues.apache.org/jira/browse/HIVE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425672#comment-13425672
]
Hudson commented on HIVE-3314:
------------------------------
Integrated in Hive-trunk-h0.21 #1578 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/1578/])
HIVE-3314 Extract global limit configuration to optimizer
(Navis via namit) (Revision 1367405)
Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=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
>
> 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=13423754&page=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