[jira] [Created] (HIVE-21978) mr data skew while druid handler indexing data
tangyun created HIVE-21978: -- Summary: mr data skew while druid handler indexing data Key: HIVE-21978 URL: https://issues.apache.org/jira/browse/HIVE-21978 Project: Hive Issue Type: Improvement Components: Druid integration Affects Versions: 3.1.1, 2.3.2 Reporter: tangyun Assignee: tangyun -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HIVE-21977) Clean up DescTableOperation
Miklos Gergely created HIVE-21977: - Summary: Clean up DescTableOperation Key: HIVE-21977 URL: https://issues.apache.org/jira/browse/HIVE-21977 Project: Hive Issue Type: Sub-task Components: Hive Affects Versions: 3.1.1 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 4.0.0 DescTable operation is messy, with some unclean solutions. It should be refactored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HIVE-21976) Offset should be null instead of zero in Calcite HiveSortLimit
Jesus Camacho Rodriguez created HIVE-21976:
--
Summary: Offset should be null instead of zero in Calcite
HiveSortLimit
Key: HIVE-21976
URL: https://issues.apache.org/jira/browse/HIVE-21976
Project: Hive
Issue Type: Bug
Components: CBO
Affects Versions: 4.0.0
Reporter: Jesus Camacho Rodriguez
Assignee: Jesus Camacho Rodriguez
Calcite expects a value equal or greater than 1. Otherwise, it may generate SQL
from a plan incorrectly ({{offset 0}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Review Request 71040: HIVE-21923 Vectorized MapJoin may miss results when only the join key is selected
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71040/ --- Review request for hive and Jesús Camacho Rodríguez. Bugs: HIVE-21923 https://issues.apache.org/jira/browse/HIVE-21923 Repository: hive-git Description --- HIVE-21923 Vectorized MapJoin may miss results when only the join key is selected Diffs - common/src/test/org/apache/hadoop/hive/common/format/datetime/package-info.java 70ee4266f45219fd81bf0d0df0a2c4380334e307 ql/src/java/org/apache/hadoop/hive/ql/exec/vector/mapjoin/VectorMapJoinInnerBigOnlyGenerateResultOperator.java 35db844f236f24d2f17f4a43d064c9ebaf8c ql/src/test/queries/clientpositive/hybridgrace_hashjoin_2.q d989ca7dc883fa071cf5772f358c68bff78f659f ql/src/test/results/clientpositive/llap/correlationoptimizer4.q.out 45a646c948ec8b72710a6b8a3949fbe0203dd68e ql/src/test/results/clientpositive/llap/hybridgrace_hashjoin_2.q.out 2305f87e45bd65152a6c77ce04f7b8efad4724d7 ql/src/test/results/clientpositive/spark/auto_join14.q.out 0c80c13889d134abe82bde30c98300620b1fd432 ql/src/test/results/clientpositive/spark/bucket_map_join_tez1.q.out 4ee669fa7dd50e0373910030b35c8860383a3a70 ql/src/test/results/clientpositive/tez/hybridgrace_hashjoin_2.q.out e28b15044503ea4bb5bd12b7caed6b105f337efd Diff: https://reviews.apache.org/r/71040/diff/1/ Testing --- Thanks, Zoltan Haindrich
[jira] [Created] (HIVE-21975) Fix incremental compilation
Zoltan Haindrich created HIVE-21975:
---
Summary: Fix incremental compilation
Key: HIVE-21975
URL: https://issues.apache.org/jira/browse/HIVE-21975
Project: Hive
Issue Type: Bug
Reporter: Zoltan Haindrich
we have an incremental compilation issue around SA ; mostly because of "?
extends Serializable"
it could be reproduced with:
{code}
git clean -dfx
mvn install -pl ql -am -DskipTests
touch `find . -name Sema*A*java` `find . -name Task*Factory.java`
mvn install -pl ql -DskipTests
{code}
error is:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile)
on project hive-exec: Compilation failure: Compilation failure:
[ERROR]
/mnt/work/hwx/hive/master/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java:[12573,60]
incompatible types: java.util.List> cannot be converted to
java.util.List>
[ERROR]
/mnt/work/hwx/hive/master/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java:[15187,49]
incompatible types: java.util.List>
cannot be converted to java.util.List>
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Review Request 70920: HIVE-21868: Vectorize CAST...FORMAT
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/70920/#review216444 --- Ship it! Ship It! - Marta Kuczora On July 4, 2019, 3:04 p.m., Karen Coppage wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/70920/ > --- > > (Updated July 4, 2019, 3:04 p.m.) > > > Review request for hive and Marta Kuczora. > > > Bugs: HIVE-21868 > https://issues.apache.org/jira/browse/HIVE-21868 > > > Repository: hive-git > > > Description > --- > > Vectorize UDFs for CAST ( AS STRING/CHAR/VARCHAR FORMAT > ) and CAST ( AS TIMESTAMP/DATE FORMAT ). > > > Diffs > - > > > common/src/java/org/apache/hadoop/hive/common/format/datetime/HiveSqlDateTimeFormatter.java > 4e024a357b > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/VectorizationContext.java > fa9d1e9783 > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastDateToCharWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastDateToString.java > dfa9f8a00d > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastDateToStringWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastDateToVarCharWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastStringToDate.java > a6dff12e1a > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastStringToDateWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastStringToTimestamp.java > b48b0136eb > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastStringToTimestampWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastTimestampToCharWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastTimestampToString.java > adc3a9d7b9 > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastTimestampToStringWithFormat.java > PRE-CREATION > > ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/CastTimestampToVarCharWithFormat.java > PRE-CREATION > ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFCastFormat.java > 16742eee9b > > ql/src/test/org/apache/hadoop/hive/ql/exec/vector/expressions/TestVectorMathFunctions.java > 663237739e > > ql/src/test/org/apache/hadoop/hive/ql/exec/vector/expressions/TestVectorTypeCasts.java > 58fd7b030e > > ql/src/test/org/apache/hadoop/hive/ql/exec/vector/expressions/TestVectorTypeCastsWithFormat.java > PRE-CREATION > ql/src/test/queries/clientnegative/udf_cast_format_bad_pattern.q > PRE-CREATION > ql/src/test/queries/clientpositive/cast_datetime_with_sql_2016_format.q > 269edf6da6 > ql/src/test/results/clientnegative/udf_cast_format_bad_pattern.q.out > PRE-CREATION > ql/src/test/results/clientpositive/cast_datetime_with_sql_2016_format.q.out > 4a502b9700 > > > Diff: https://reviews.apache.org/r/70920/diff/5/ > > > Testing > --- > > > Thanks, > > Karen Coppage > >
[jira] [Created] (HIVE-21974) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.
mahesh kumar behera created HIVE-21974: -- Summary: The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma. Key: HIVE-21974 URL: https://issues.apache.org/jira/browse/HIVE-21974 Project: Hive Issue Type: Sub-task Components: repl Reporter: mahesh kumar behera Assignee: mahesh kumar behera REPL DUMP fetches the events from NOTIFICATION_LOG table based on regular expression + inclusion/exclusion list. So, in case of rename table event, the event will be ignored if old table doesn't match the pattern but the new table should be bootstrapped. REPL DUMP should have a mechanism to detect such tables and automatically bootstrap with incremental replication.Also, if renamed table is excluded from replication policy, then need to drop the old table at target as well. There are 4 scenarios that needs to be handled. # Both new name and old name satisfies the table name pattern filter. ## No need to do anything. The incremental event for rename should take care of the replication. # Both the names does not satisfy the table name pattern filter. ## Both the names are not in the scope of the policy and thus nothing needs to be done. # New name satisfies the pattern but the old name does not. ## The table will not be present at the target. ## Rename event handler for dump should detect this case and add the new table name to the list of table for bootstrap. ## All the events related to the table (new name) should be ignored. ## If there is a drop event for the table (with new name), then remove the table from the list of tables to be bootstrapped. ## In case of rename (double rename) ### If the new name satisfies the table pattern, then add the new name to the list of tables to be bootstrapped and remove the old name from the list of tables to be bootstrapped. ### If the new name does not satisfies then just removed the table name from the list of tables to be bootstrapped. # New name does not satisfies the pattern but the old name satisfies. ## Change the rename event to a drop event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
