[jira] [Created] (HIVE-18803) Add DROP To hive.mapred.mode Strict List
BELUGA BEHR created HIVE-18803:
--
Summary: Add DROP To hive.mapred.mode Strict List
Key: HIVE-18803
URL: https://issues.apache.org/jira/browse/HIVE-18803
Project: Hive
Issue Type: Improvement
Components: HiveServer2
Affects Versions: 3.0.0
Reporter: BELUGA BEHR
Do not allow a user to DROP DATABASE / DROP TABLE if {{hive.mapred.mode}} is
set to 'strict'. This will help prevent accidental drops, if the user chooses
to.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HIVE-18802) Incorrect results when referencing same Accumulo table multiple times in one query
Anthony Hsu created HIVE-18802:
--
Summary: Incorrect results when referencing same Accumulo table
multiple times in one query
Key: HIVE-18802
URL: https://issues.apache.org/jira/browse/HIVE-18802
Project: Hive
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Anthony Hsu
While investigating HIVE-18695, I noticed incorrect results returned by the
following Accumulo query:
{code:java}
DROP TABLE accumulo_test;
CREATE TABLE accumulo_test(key int, value int)
STORED BY 'org.apache.hadoop.hive.accumulo.AccumuloStorageHandler'
WITH SERDEPROPERTIES ("accumulo.columns.mapping" = ":rowID,cf:string")
TBLPROPERTIES ("accumulo.table.name" = "accumulo_table_0");
INSERT OVERWRITE TABLE accumulo_test VALUES (0,0), (1,1), (2,2), (3,3);
SELECT * from accumulo_test where key == 1 union all select * from
accumulo_test where key == 2;{code}
The expected output is
{code:java}
1 1
2 2{code}
but the actual output is
{code:java}
1 0
1 1
1 2
1 3
2 0
2 1
2 2
2 3
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HIVE-18801) MERGE INTO SQL not work fully
xiaolo created HIVE-18801:
-
Summary: MERGE INTO SQL not work fully
Key: HIVE-18801
URL: https://issues.apache.org/jira/browse/HIVE-18801
Project: Hive
Issue Type: Bug
Components: Clients
Affects Versions: 2.3.2
Environment: CREATE TABLE transactions(
id int,
name string
)
PARTITIONED BY (partition_date string)
CLUSTERED BY (ID) into 5 buckets
STORED AS ORC TBLPROPERTIES ('transactional'='true');
CREATE TABLE merge_source(
id int,
name string);
Reporter: xiaolo
*Here is three sql:*
*1:*
*MERGE INTO transactions AS T*
*USING merge_source AS S*
*ON T.id = S.id*
*WHEN MATCHED THEN UPDATE SET name='update' ;*
*2:***
*MERGE INTO transactions AS T*
*USING merge_source AS S*
*ON T.id = S.id*
*WHEN NOT MATCHED THEN INSERT VALUES (S.ID, S.NAME,'321');*
*3:***
*MERGE INTO transactions AS T*
*USING merge_source AS S*
*ON T.id = S.id*
*WHEN MATCHED THEN UPDATE SET name='update'*
*WHEN NOT MATCHED THEN INSERT VALUES (S.ID, S.NAME,'321');*
*There is no error log , just the table rows is not expected when i run sql3 ,
it looks like nothing changed.*
*finally*
*I need use sql1 and sql2 to replace sql3 , and to make sure the table rows is*
*expected .***
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Review Request 65801: HIVE-18797 ExprConstNodeDesc's getExprString should put appropriate qualifier with literals
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/65801/ --- (Updated Feb. 26, 2018, 1:03 a.m.) Review request for hive and Ashutosh Chauhan. Bugs: HIVE-18797 https://issues.apache.org/jira/browse/HIVE-18797 Repository: hive-git Description --- See JIRA Diffs (updated) - hbase-handler/src/test/results/positive/hbase_timestamp.q.out e719b087d4 ql/src/java/org/apache/hadoop/hive/ql/plan/ExprNodeConstantDesc.java 73f449fc28 ql/src/test/results/clientpositive/annotate_stats_deep_filters.q.out ab8c22b9be ql/src/test/results/clientpositive/annotate_stats_groupby.q.out 25efe1e1f4 ql/src/test/results/clientpositive/annotate_stats_groupby2.q.out 78c4808f5f ql/src/test/results/clientpositive/annotate_stats_select.q.out 9aaa6f68a2 ql/src/test/results/clientpositive/cast_on_constant.q.out 7f920f41af ql/src/test/results/clientpositive/constant_prop_3.q.out b754f8e7b4 ql/src/test/results/clientpositive/constantfolding.q.out c4fce25e41 ql/src/test/results/clientpositive/constprog_type.q.out 27ef1f482b ql/src/test/results/clientpositive/druid_basic2.q.out 08b64d6d82 ql/src/test/results/clientpositive/druid_basic3.q.out ce6d0aafed ql/src/test/results/clientpositive/druid_intervals.q.out c94cbe9bd4 ql/src/test/results/clientpositive/druid_timeseries.q.out 785cbd2114 ql/src/test/results/clientpositive/druid_topn.q.out 90eec3dd49 ql/src/test/results/clientpositive/except_all.q.out c3310f5154 ql/src/test/results/clientpositive/extrapolate_part_stats_date.q.out 8fea7fdf44 ql/src/test/results/clientpositive/fold_eq_with_case_when.q.out 49e0d35d39 ql/src/test/results/clientpositive/groupby_cube1.q.out 37b8c62edd ql/src/test/results/clientpositive/groupby_cube_multi_gby.q.out e6126ab2c6 ql/src/test/results/clientpositive/groupby_grouping_id3.q.out ac43413400 ql/src/test/results/clientpositive/groupby_grouping_sets1.q.out 62fc9fb550 ql/src/test/results/clientpositive/groupby_grouping_sets2.q.out 43e17ec6bc ql/src/test/results/clientpositive/groupby_grouping_sets3.q.out 352d4beb9f ql/src/test/results/clientpositive/groupby_grouping_sets4.q.out e368e1ee12 ql/src/test/results/clientpositive/groupby_grouping_sets5.q.out 1766fb9bbc ql/src/test/results/clientpositive/groupby_grouping_sets6.q.out 563b110a11 ql/src/test/results/clientpositive/groupby_grouping_sets_grouping.q.out 1f2cd456c8 ql/src/test/results/clientpositive/groupby_grouping_sets_limit.q.out efa1802855 ql/src/test/results/clientpositive/groupby_grouping_window.q.out 0f58f5182a ql/src/test/results/clientpositive/groupby_rollup1.q.out a849a8d368 ql/src/test/results/clientpositive/groupby_rollup_empty.q.out dd53fe2140 ql/src/test/results/clientpositive/having.q.out 8a630751bb ql/src/test/results/clientpositive/having2.q.out 67f8af8328 ql/src/test/results/clientpositive/implicit_cast1.q.out 6e1706a8a3 ql/src/test/results/clientpositive/infer_bucket_sort_grouping_operators.q.out 72249383ee ql/src/test/results/clientpositive/infer_const_type.q.out 647c910241 ql/src/test/results/clientpositive/interval_alt.q.out 53c1be8d05 ql/src/test/results/clientpositive/interval_arithmetic.q.out eba97face9 ql/src/test/results/clientpositive/limit_pushdown2.q.out f4cff2bcc0 ql/src/test/results/clientpositive/literal_ints.q.out 9a56ebd5eb ql/src/test/results/clientpositive/llap/acid_vectorization_original.q.out 68801f0294 ql/src/test/results/clientpositive/llap/current_date_timestamp.q.out 98ede4e995 ql/src/test/results/clientpositive/llap/dynamic_semijoin_reduction_3.q.out aca6b21dba ql/src/test/results/clientpositive/llap/dynpart_sort_opt_vectorization.q.out 15a97a78c1 ql/src/test/results/clientpositive/llap/dynpart_sort_optimization.q.out 78b9a443b8 ql/src/test/results/clientpositive/llap/enforce_constraint_notnull.q.out 7b1dd40a16 ql/src/test/results/clientpositive/llap/except_distinct.q.out 1e5937a22d ql/src/test/results/clientpositive/llap/explainuser_1.q.out 43ca0d9ad7 ql/src/test/results/clientpositive/llap/groupby_rollup_empty.q.out 24be36ea36 ql/src/test/results/clientpositive/llap/having.q.out 75de96ab59 ql/src/test/results/clientpositive/llap/intersect_all.q.out 20a234e53b ql/src/test/results/clientpositive/llap/intersect_distinct.q.out a5384eb196 ql/src/test/results/clientpositive/llap/intersect_merge.q.out 6f0e7f1f66 ql/src/test/results/clientpositive/llap/lineage2.q.out 4f59a4d59b ql/src/test/results/clientpositive/llap/lineage3.q.out ca4405caf7 ql/src/test/results/clientpositive/llap/mrr.q.out bfa26e4ff8 ql/src/test/results/clientpositive/llap/multi_count_distinct_null.q.out 66bf74f15a ql/src/test/results/clientpositive/llap/orc_merge5.q.out 6eba365ff2 ql/src/test/results/clientpositive/llap/orc_merge6.q.out
[jira] [Created] (HIVE-18800) Vectorization: VectorCoalesce doesn't handle the all repeated NULLs case
Matt McCline created HIVE-18800: --- Summary: Vectorization: VectorCoalesce doesn't handle the all repeated NULLs case Key: HIVE-18800 URL: https://issues.apache.org/jira/browse/HIVE-18800 Project: Hive Issue Type: Bug Components: Hive Affects Versions: 3.0.0 Reporter: Matt McCline Assignee: Matt McCline Fix for HIVE-18622 broken the case when all columns are repeated NULLs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
