You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vincenz Priesnitz (Jira)" <ji...@apache.org> on 2020/11/04 19:21:00 UTC

[jira] [Comment Edited] (HIVE-24353) performance: Refactor TimestampTZ parsing

    [ https://issues.apache.org/jira/browse/HIVE-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226351#comment-17226351 ] 

Vincenz Priesnitz edited comment on HIVE-24353 at 11/4/20, 7:20 PM:
--------------------------------------------------------------------

[~belugabehr] I think this is unrelated actually. 
 I have submitted a PR but it is not showing up here yet: [https://github.com/apache/hive/pull/1650]

I hope this clarifies the issue being independent from the other ticket.


was (Author: vince83):
[~belugabehr] I think this is unrelated actually. 
I have submitted a PR but it is not showing up here yet. I think this may clarify the issue. 

> performance: Refactor TimestampTZ parsing
> -----------------------------------------
>
>                 Key: HIVE-24353
>                 URL: https://issues.apache.org/jira/browse/HIVE-24353
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vincenz Priesnitz
>            Priority: Minor
>
> I found that for datasets that contain a lot of timestamps (without timezones) hive spends the majority of time in TimestampTZUtil.parse, in particular constructing stractraces for the try-catch blocks. 
> When parsing TimestampTZ we are currently using a fallback chain with several try-catch blocks. For a common timestamp string without a timezone, we currently throw and catch 2 exceptions, and actually parse the string twice. 
> I propose a refactor, that parses the string once and then expresses the fallback chain with queries to the parsed TemporalAccessor. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)