[jira] [Created] (HIVE-26155) Create a new connection pool for compaction
Antal Sinkovits created HIVE-26155: -- Summary: Create a new connection pool for compaction Key: HIVE-26155 URL: https://issues.apache.org/jira/browse/HIVE-26155 Project: Hive Issue Type: Improvement Components: Standalone Metastore Reporter: Antal Sinkovits Assignee: Antal Sinkovits Currently the TxnHandler uses 2 connection pools to communicate with the HMS: the default one and one for mutexing. If compaction is configured incorrectly (e.g. too many Initiators are running on the same db) then compaction can use up all the connections in the default connection pool and all user queries can get stuck. We should have a separate connection pool (configurable size) just for compaction-related activities. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (HIVE-26154) CLONE - Upgrade cron-utils to 9.1.6
Asif Saleh created HIVE-26154: - Summary: CLONE - Upgrade cron-utils to 9.1.6 Key: HIVE-26154 URL: https://issues.apache.org/jira/browse/HIVE-26154 Project: Hive Issue Type: Task Components: Hive Affects Versions: 3.1.3, 4.0.0 Reporter: Asif Saleh To fix [CVE-2021-41269|https://nvd.nist.gov/vuln/detail/CVE-2021-41269] issue. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (HIVE-26153) CVE-2021-27568
Asif Saleh created HIVE-26153:
-
Summary: CVE-2021-27568
Key: HIVE-26153
URL: https://issues.apache.org/jira/browse/HIVE-26153
Project: Hive
Issue Type: Bug
Components: Hive
Affects Versions: 3.1.3
Reporter: Asif Saleh
Address the vulnerability CVE-2021-27568.
Hive jdbc driver is packaged with json-smart version which has the above
vulnerability.
An issue was discovered in netplex json-smart-v1 through 2015-10-23 and
json-smart-v2 through 2.4. An exception is thrown from a function, but it is
not caught, as demonstrated by NumberFormatException. When it is not caught, it
may cause programs using the library to crash or expose sensitive information.
Fix: Upgrade {{net.minidev:json-smart}} to version 1.3.2, 2.4.1 or higher.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (HIVE-26152) Compilation fails with Maven 3.8.5
Tony Torralba created HIVE-26152:
Summary: Compilation fails with Maven 3.8.5
Key: HIVE-26152
URL: https://issues.apache.org/jira/browse/HIVE-26152
Project: Hive
Issue Type: Bug
Affects Versions: 3.1.3
Reporter: Tony Torralba
When trying to build Hive with Maven 3.8.5 on latest {{{}master{}}}, the build
fails because of a name clash in a class between {{kyro4}} and {{{}kyro5{}}}:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile)
on project hive-kryo-registrator: Compilation failure: Compilation failure:
[ERROR]
/tmp/hive/kryo-registrator/src/main/java/org/apache/hive/spark/HiveKryoRegistrator.java:[41,18]
org.apache.hive.spark.HiveKryoRegistrator.HiveKeySerializer is not abstract
and does not override abstract method
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class)
in com.esotericsoftware.kryo.Serializer[ERROR]
/tmp/hive/kryo-registrator/src/main/java/org/apache/hive/spark/HiveKryoRegistrator.java:[49,20]
name clash:
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class) in
org.apache.hive.spark.HiveKryoRegistrator.HiveKeySerializer and
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class)
in com.esotericsoftware.kryo.Serializer have the same erasure, yet neither
overrides the other[ERROR]
/tmp/hive/kryo-registrator/src/main/java/org/apache/hive/spark/HiveKryoRegistrator.java:[57,10]
org.apache.hive.spark.HiveKryoRegistrator.BytesWritableSerializer is not
abstract and does not override abstract method
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class)
in com.esotericsoftware.kryo.Serializer[ERROR]
/tmp/hive/kryo-registrator/src/main/java/org/apache/hive/spark/HiveKryoRegistrator.java:[64,26]
name clash:
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class) in
org.apache.hive.spark.HiveKryoRegistrator.BytesWritableSerializer and
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class)
in com.esotericsoftware.kryo.Serializer have the same erasure, yet neither
overrides the other [ERROR]
/tmp/hive/kryo-registrator/src/main/java/org/apache/hive/spark/NoHashCodeKryoSerializer.java:[51,18]
org.apache.hive.spark.NoHashCodeKryoSerializer.HiveKeySerializer is not
abstract and does not override abstract method
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class)
in com.esotericsoftware.kryo.Serializer[ERROR]
/tmp/hive/kryo-registrator/src/main/java/org/apache/hive/spark/NoHashCodeKryoSerializer.java:[58,20]
name clash:
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class) in
org.apache.hive.spark.NoHashCodeKryoSerializer.HiveKeySerializer and
read(com.esotericsoftware.kryo.Kryo,com.esotericsoftware.kryo.io.Input,java.lang.Class)
in com.esotericsoftware.kryo.Serializer have the same erasure, yet neither
overrides the other{code}
Build command:
{code:java}
mvn clean package -DskipTests -Dmaven.javadoc.skip=true -Drat.skip=true {code}
(Had to skip the RAT check because it complained about a lot of files not
having approved licenses).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (HIVE-26151) Support range-based time travel queries for Iceberg
Marton Bod created HIVE-26151: - Summary: Support range-based time travel queries for Iceberg Key: HIVE-26151 URL: https://issues.apache.org/jira/browse/HIVE-26151 Project: Hive Issue Type: New Feature Reporter: Marton Bod Assignee: Marton Bod Allow querying which records have been inserted during a certain time window for Iceberg tables. The Iceberg TableScan API provides an implementation for that, so most of the work would go into adding syntax support and transporting the startTime and endTime parameters to the Iceberg input format. Proposed new syntax: SELECT * FROM table FOR SYSTEM_TIME FROM '' TO '' SELECT * FROM table FOR SYSTEM_VERSION FROM TO (the TO clause is optional in both cases) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (HIVE-26150) OrcRawRecordMerger reads each row twice
Alessandro Solimando created HIVE-26150: --- Summary: OrcRawRecordMerger reads each row twice Key: HIVE-26150 URL: https://issues.apache.org/jira/browse/HIVE-26150 Project: Hive Issue Type: Bug Components: ORC, Transactions Affects Versions: 4.0.0-alpha-2 Reporter: Alessandro Solimando OrcRawRecordMerger reads each row twice, the issue does not surface since the merger is only used with the parameter "collapseEvents" as true, which filters out one of the two rows. collapseEvents true and false should produce the same result, since in current acid implementation, each event has a distinct rowid, so two identical rows cannot be there, this is the case only for the bug. In order to reproduce the issue, it is sufficient to set the second parameter to false [here|https://github.com/apache/hive/blob/61d4ff2be48b20df9fd24692c372ee9c2606babe/ql/src/java/org/apache/hadoop/hive/ql/io/orc/OrcInputFormat.java#L2103-L2106], and run tests in TestOrcRawRecordMerger and observe two tests failing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
