[ https://issues.apache.org/jira/browse/HIVE-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749311#comment-13749311 ]
Phabricator commented on HIVE-5137: ----------------------------------- thejas has commented on the revision "HIVE-5137 [jira] A Hive SQL query should not return a ResultSet when the underlying plan does not include a FetchTaskSQL". LGTM +1 REVISION DETAIL https://reviews.facebook.net/D12453 To: JIRA, vaibhavgumashta Cc: thejas > A Hive SQL query should not return a ResultSet when the underlying plan does > not include a FetchTask > ---------------------------------------------------------------------------------------------------- > > Key: HIVE-5137 > URL: https://issues.apache.org/jira/browse/HIVE-5137 > Project: Hive > Issue Type: Bug > Components: HiveServer2 > Affects Versions: 0.11.0 > Reporter: Vaibhav Gumashta > Assignee: Vaibhav Gumashta > Fix For: 0.11.0 > > Attachments: HIVE-5137.D12453.1.patch, HIVE-5137.D12453.2.patch, > HIVE-5137.D12453.3.patch, HIVE-5137.D12453.4.patch, HIVE-5137.D12453.5.patch, > HIVE-5137.D12453.6.patch, HIVE-5137.D12453.7.patch > > > Currently, a query like "create table if not exists t2 as select * from t1" > sets the hasResultSet to true in SQLOperation and in turn, the query returns > a result set. However, as a DDL command, this should ideally not return a > result set. -- 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