[jira] [Created] (HIVE-22170) from_unixtime and unix_timestamp should use user session time zone

[Jesus Camacho Rodriguez (Jira)]

Jesus Camacho Rodriguez created HIVE-22170:
--

 Summary: from_unixtime and unix_timestamp should use user session 
time zone
 Key: HIVE-22170
 URL: https://issues.apache.org/jira/browse/HIVE-22170
 Project: Hive
  Issue Type: Bug
Affects Versions: 3.1.2, 3.1.1, 3.1.0, 4.0.0, 3.2.0
Reporter: Jesus Camacho Rodriguez
Assignee: Jesus Camacho Rodriguez


According to documentation, that is the expected behavior (since session time 
zone was not present, system time zone was being used previously). This was 
incorrectly changed by HIVE-12192 / HIVE-20007. This JIRA should fix this issue.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HIVE-22169) Tez: SplitGenerator tries to look for plan files which won't exist for Tez

[Gopal V (Jira)]

Gopal V created HIVE-22169:
--

 Summary: Tez: SplitGenerator tries to look for plan files which 
won't exist for Tez
 Key: HIVE-22169
 URL: https://issues.apache.org/jira/browse/HIVE-22169
 Project: Hive
  Issue Type: Bug
Reporter: Gopal V


{code}
at 
org.apache.hadoop.hive.ql.exec.Utilities.clearWork(Utilities.java:310)
at 
org.apache.hadoop.hive.ql.exec.tez.HiveSplitGenerator.initialize(HiveSplitGenerator.java:318)
at 
org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable$1.run(RootInputInitializerManager.java:278)
at 
org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable$1.run(RootInputInitializerManager.java:269)
at java.security.AccessController.doPrivileged(Native Method
{code}

The split generator tries to clear out the work items from HDFS, which will 
never exist for Tez plans.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HIVE-22168) remove excessive logging by llap cache.

[slim bouguerra (Jira)]

slim bouguerra created HIVE-22168:
-

 Summary: remove excessive logging by llap cache.
 Key: HIVE-22168
 URL: https://issues.apache.org/jira/browse/HIVE-22168
 Project: Hive
  Issue Type: Improvement
  Components: llap, Logging
Reporter: slim bouguerra
Assignee: slim bouguerra


Lllap cache logging is very expensive when it comes to log every request 
buffers range.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Hit HIVE-13023 with 2.0.1 maven artifacts

[Rui Li]

Hello guys,

I hit HIVE-13023  when I
programmatically executed some queries with Hive-2.0.1. I did some
investigation and there seemed to be some issues with the 2.0.1 artifacts
we published.
I compared the hive-exec artifact from maven central

with
the jar in our binary distribution
,
and the two hive-exec jars are of different sizes.
I also decompiled these two jars to check the offending method
*StorageFormat::fillStorageFormat*. It turned out the jar from maven got
the ordinals of some tokens wrong (the ordinal of TOK_FILEFORMAT_GENERIC
should be 715):
[image: 屏幕快照 2019-09-04 下午5.08.59.png]

And the jar in our distribution has the correct ordinals:
[image: 屏幕快照 2019-09-04 下午5.14.00.png]

I wonder whether anybody could help verify the issue, and whether it's
possible to update the published jars if the issue is valid?

-- 
Best regards!
Rui Li