[jira] [Created] (HIVE-24536) Upgrade ORC to 1.6.6
Dongjoon Hyun created HIVE-24536: Summary: Upgrade ORC to 1.6.6 Key: HIVE-24536 URL: https://issues.apache.org/jira/browse/HIVE-24536 Project: Hive Issue Type: New Feature Components: ORC Affects Versions: 4.0.0 Reporter: Dongjoon Hyun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24316) Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1
Dongjoon Hyun created HIVE-24316: Summary: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 Key: HIVE-24316 URL: https://issues.apache.org/jira/browse/HIVE-24316 Project: Hive Issue Type: Bug Components: ORC Affects Versions: 3.1.3 Reporter: Dongjoon Hyun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24222) Upgrade ORC to 1.5.12
Dongjoon Hyun created HIVE-24222: Summary: Upgrade ORC to 1.5.12 Key: HIVE-24222 URL: https://issues.apache.org/jira/browse/HIVE-24222 Project: Hive Issue Type: Bug Components: ORC Affects Versions: 4.0.0 Reporter: Dongjoon Hyun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24030) Upgrade ORC to 1.5.10
Dongjoon Hyun created HIVE-24030: Summary: Upgrade ORC to 1.5.10 Key: HIVE-24030 URL: https://issues.apache.org/jira/browse/HIVE-24030 Project: Hive Issue Type: Bug Components: ORC Affects Versions: 4.0.0 Reporter: Dongjoon Hyun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-19658) Update Hive to use ORC 1.4.4
Dongjoon Hyun created HIVE-19658: Summary: Update Hive to use ORC 1.4.4 Key: HIVE-19658 URL: https://issues.apache.org/jira/browse/HIVE-19658 Project: Hive Issue Type: Bug Components: ORC Affects Versions: 3.0.0 Reporter: Dongjoon Hyun ORC 1.4.4 (released on May 14th) includes nine fixes. This issue aims to update Hive to use it. https://issues.apache.org/jira/issues/?filter=12342568=project%20%3D%20ORC%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.4.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HIVE-19497) SessionHiveMetaStoreClient.getTable should respect default catalog
Dongjoon Hyun created HIVE-19497: Summary: SessionHiveMetaStoreClient.getTable should respect default catalog Key: HIVE-19497 URL: https://issues.apache.org/jira/browse/HIVE-19497 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 3.0.0 Reporter: Dongjoon Hyun Currently, SessionHiveMetaStoreClient always use `DEFAULT_CATALOG_NAME` during looking up the underlying tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HIVE-17186) `double` type constant operation loses precision
Dongjoon Hyun created HIVE-17186:
Summary: `double` type constant operation loses precision
Key: HIVE-17186
URL: https://issues.apache.org/jira/browse/HIVE-17186
Project: Hive
Issue Type: Bug
Reporter: Dongjoon Hyun
This might be an issue where Hive loses a precision and generates a wrong
result when handling *double* constant operations. This was reported in the
following environment.
*ENVIRONMENT*
https://github.com/hortonworks/hive-testbench/blob/hive14/tpch-gen/ddl/orc.sql
*SQL*
{code}
hive> explain select l_discount from lineitem where l_discount between 0.06 -
0.01 and 0.06 + 0.01 limit 10;
OK
Plan not optimized by CBO.
Stage-0
Fetch Operator
limit:10
Stage-1
Map 1 vectorized
File Output Operator [FS_9]
compressed:false
Statistics:Num rows: 10 Data size: 80 Basic stats: COMPLETE Column
stats: COMPLETE
table:{"input
format:":"org.apache.hadoop.mapred.TextInputFormat","output
format:":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat","serde:":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe"}
Limit [LIM_8]
Number of rows:10
Statistics:Num rows: 10 Data size: 80 Basic stats: COMPLETE
Column stats: COMPLETE
Select Operator [OP_7]
outputColumnNames:["_col0"]
Statistics:Num rows: 294854 Data size: 2358832 Basic
stats: COMPLETE Column stats: COMPLETE
Filter Operator [FIL_6]
predicate:l_discount BETWEEN 0.049996 AND
0.06999 (type: boolean)
Statistics:Num rows: 294854 Data size: 2358832
Basic stats: COMPLETE Column stats: COMPLETE
TableScan [TS_0]
alias:lineitem
Statistics:Num rows: 589709 Data size:
4832986297043 Basic stats: COMPLETE Column stats: COMPLETE
hive> select max(l_discount) from lineitem where l_discount between 0.06 - 0.01
and 0.06 + 0.01 limit 10;
OK
0.06
Time taken: 314.923 seconds, Fetched: 1 row(s)
{code}
Hive excludes 0.07 differently from the users' intuitiion. Also, this
difference makes some users confused because they believe that Hive's result is
the correct one. Is there any way for Hive to fix this?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
