You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/07/05 22:22:00 UTC
[jira] [Work logged] (HIVE-23699) Cleanup HIVEQUERYRESULTFILEFORMAT
handling
[ https://issues.apache.org/jira/browse/HIVE-23699?focusedWorklogId=454657&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-454657 ]
ASF GitHub Bot logged work on HIVE-23699:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jul/20 22:21
Start Date: 05/Jul/20 22:21
Worklog Time Spent: 10m
Work Description: jcamachor commented on pull request #1119:
URL: https://github.com/apache/hive/pull/1119#issuecomment-653946171
@jfsii , can we trigger tests again? Thanks
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 454657)
Time Spent: 50m (was: 40m)
> Cleanup HIVEQUERYRESULTFILEFORMAT handling
> ------------------------------------------
>
> Key: HIVE-23699
> URL: https://issues.apache.org/jira/browse/HIVE-23699
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 4.0.0
> Reporter: John Sherman
> Assignee: John Sherman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> HIVEQUERYRESULTFILEFORMAT format handling has grown over the years and has become somewhat messy code wise in SemanticAnalyzer and TaskCompiler. There are special cases where the HIVEQUERYRESULTFILEFORMAT setting gets changed at runtime that may cause issues if a user changes execution.engines between queries and probably other corner cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)