[jira] [Assigned] (HIVE-23985) flaky TestMiniHiveKafkaCliDriver.testCliDriver[kafka_storage_handler]
[ https://issues.apache.org/jira/browse/HIVE-23985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] KIRTI RUGE reassigned HIVE-23985: - Assignee: KIRTI RUGE > flaky TestMiniHiveKafkaCliDriver.testCliDriver[kafka_storage_handler] > - > > Key: HIVE-23985 > URL: https://issues.apache.org/jira/browse/HIVE-23985 > Project: Hive > Issue Type: Bug >Reporter: Zoltan Haindrich >Assignee: KIRTI RUGE >Priority: Major > > http://ci.hive.apache.org/job/hive-precommit/job/master/144/testReport/junit/org.apache.hadoop.hive.cli/TestMiniHiveKafkaCliDriver/Testing___split_16___Archive___testCliDriver_kafka_storage_handler_/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-23548) TestActivePassiveHA is unstable
[ https://issues.apache.org/jira/browse/HIVE-23548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] KIRTI RUGE reassigned HIVE-23548: - Assignee: KIRTI RUGE > TestActivePassiveHA is unstable > --- > > Key: HIVE-23548 > URL: https://issues.apache.org/jira/browse/HIVE-23548 > Project: Hive > Issue Type: Sub-task >Reporter: Zoltan Haindrich >Assignee: KIRTI RUGE >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-24569) LLAP daemon leaks file descriptors/log4j appenders
[
https://issues.apache.org/jira/browse/HIVE-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sankar Hariappan updated HIVE-24569:
Fix Version/s: (was: 3.1.3)
> LLAP daemon leaks file descriptors/log4j appenders
> --
>
> Key: HIVE-24569
> URL: https://issues.apache.org/jira/browse/HIVE-24569
> Project: Hive
> Issue Type: Bug
> Components: llap
>Affects Versions: 2.2.0
>Reporter: Stamatis Zampetakis
>Assignee: Stamatis Zampetakis
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
> Attachments: llap-appender-gc-roots.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> With HIVE-9756 query logs in LLAP are directed to different files (file per
> query) using a Log4j2 routing appender. Without a purge policy in place,
> appenders are created dynamically by the routing appender, one for each
> query, and remain in memory forever. The dynamic appenders write to files so
> each appender holds to a file descriptor.
> Further work HIVE-14224 has mitigated the issue by introducing a custom
> purging policy (LlapRoutingAppenderPurgePolicy) which deletes the dynamic
> appenders (and closes the respective files) when the query is completed
> (org.apache.hadoop.hive.llap.daemon.impl.QueryTracker#handleLogOnQueryCompletion).
>
> However, in the presence of multiple threads appending to the logs there are
> race conditions. In an internal Hive cluster the number of file descriptors
> started going up approx one descriptor leaking per query. After some
> debugging it turns out that one thread (running the
> QueryTracker#handleLogOnQueryCompletion) signals that the query has finished
> and thus the purge policy should get rid of the respective appender (and
> close the file) while another (Task-Executor-0) attempts to append another
> log message for the same query. The initial appender is closed after the
> request from the query tracker but a new one is created to accomodate the
> message from the task executor and the latter is never removed thus creating
> a leak.
> Similar leaks have been identified and fixed for HS2 with the most similar
> one being that described
> [here|https://issues.apache.org/jira/browse/HIVE-22753?focusedCommentId=17021041=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17021041].
>
> The problem relies on the timing of threads so it may not manifestate in all
> versions between 2.2.0 and 4.0.0. Usually the leak can be seen either via
> lsof (or other similar command) with the following output:
> {noformat}
> # 1494391 is the PID of the LLAP daemon process
> ls -ltr /proc/1494391/fd
> ...
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 978 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121724_66ce273d-54a9-4dcd-a9fb-20cb5691cef7-dag_1608659125567_0008_194.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 977 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121804_ce53eeb5-c73f-4999-b7a4-b4dd04d4e4de-dag_1608659125567_0008_197.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 974 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224122002_1693bd7d-2f0e-4673-a8d1-b7cb14a02204-dag_1608659125567_0008_204.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 989 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121909_6a56218f-06c7-4906-9907-4b6dd824b100-dag_1608659125567_0008_201.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 984 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121754_78ef49a0-bc23-478f-9a16-87fa25e7a287-dag_1608659125567_0008_196.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 983 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121855_e65b9ebf-b2ec-4159-9570-1904442b7048-dag_1608659125567_0008_200.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 981 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121818_e9051ae3-1316-46af-aabb-22c53ed2fda7-dag_1608659125567_0008_198.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 980 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121744_fcf37921-4351-4368-95ee-b5be2592d89a-dag_1608659125567_0008_195.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 979 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121837_e80c0024-f6bc-4b3c-85ed-5c0c85c55787-dag_1608659125567_0008_199.log
>
[jira] [Work logged] (HIVE-27209) Backport HIVE-24569: LLAP daemon leaks file descriptors/log4j appenders
[ https://issues.apache.org/jira/browse/HIVE-27209?focusedWorklogId=855685=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855685 ] ASF GitHub Bot logged work on HIVE-27209: - Author: ASF GitHub Bot Created on: 10/Apr/23 04:17 Start Date: 10/Apr/23 04:17 Worklog Time Spent: 10m Work Description: sankarh commented on PR #4193: URL: https://github.com/apache/hive/pull/4193#issuecomment-1501373334 @guptanikhil007 Why test changes are not ported? Issue Time Tracking --- Worklog Id: (was: 855685) Time Spent: 50m (was: 40m) > Backport HIVE-24569: LLAP daemon leaks file descriptors/log4j appenders > --- > > Key: HIVE-27209 > URL: https://issues.apache.org/jira/browse/HIVE-27209 > Project: Hive > Issue Type: Sub-task > Components: llap >Affects Versions: 2.2.0 >Reporter: Nikhil Gupta >Assignee: Nikhil Gupta >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-24569) LLAP daemon leaks file descriptors/log4j appenders
[
https://issues.apache.org/jira/browse/HIVE-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sankar Hariappan updated HIVE-24569:
Fix Version/s: 3.1.3
> LLAP daemon leaks file descriptors/log4j appenders
> --
>
> Key: HIVE-24569
> URL: https://issues.apache.org/jira/browse/HIVE-24569
> Project: Hive
> Issue Type: Bug
> Components: llap
>Affects Versions: 2.2.0
>Reporter: Stamatis Zampetakis
>Assignee: Stamatis Zampetakis
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.1.3, 4.0.0-alpha-1
>
> Attachments: llap-appender-gc-roots.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> With HIVE-9756 query logs in LLAP are directed to different files (file per
> query) using a Log4j2 routing appender. Without a purge policy in place,
> appenders are created dynamically by the routing appender, one for each
> query, and remain in memory forever. The dynamic appenders write to files so
> each appender holds to a file descriptor.
> Further work HIVE-14224 has mitigated the issue by introducing a custom
> purging policy (LlapRoutingAppenderPurgePolicy) which deletes the dynamic
> appenders (and closes the respective files) when the query is completed
> (org.apache.hadoop.hive.llap.daemon.impl.QueryTracker#handleLogOnQueryCompletion).
>
> However, in the presence of multiple threads appending to the logs there are
> race conditions. In an internal Hive cluster the number of file descriptors
> started going up approx one descriptor leaking per query. After some
> debugging it turns out that one thread (running the
> QueryTracker#handleLogOnQueryCompletion) signals that the query has finished
> and thus the purge policy should get rid of the respective appender (and
> close the file) while another (Task-Executor-0) attempts to append another
> log message for the same query. The initial appender is closed after the
> request from the query tracker but a new one is created to accomodate the
> message from the task executor and the latter is never removed thus creating
> a leak.
> Similar leaks have been identified and fixed for HS2 with the most similar
> one being that described
> [here|https://issues.apache.org/jira/browse/HIVE-22753?focusedCommentId=17021041=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17021041].
>
> The problem relies on the timing of threads so it may not manifestate in all
> versions between 2.2.0 and 4.0.0. Usually the leak can be seen either via
> lsof (or other similar command) with the following output:
> {noformat}
> # 1494391 is the PID of the LLAP daemon process
> ls -ltr /proc/1494391/fd
> ...
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 978 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121724_66ce273d-54a9-4dcd-a9fb-20cb5691cef7-dag_1608659125567_0008_194.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 977 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121804_ce53eeb5-c73f-4999-b7a4-b4dd04d4e4de-dag_1608659125567_0008_197.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 974 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224122002_1693bd7d-2f0e-4673-a8d1-b7cb14a02204-dag_1608659125567_0008_204.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 989 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121909_6a56218f-06c7-4906-9907-4b6dd824b100-dag_1608659125567_0008_201.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 984 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121754_78ef49a0-bc23-478f-9a16-87fa25e7a287-dag_1608659125567_0008_196.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 983 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121855_e65b9ebf-b2ec-4159-9570-1904442b7048-dag_1608659125567_0008_200.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 981 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121818_e9051ae3-1316-46af-aabb-22c53ed2fda7-dag_1608659125567_0008_198.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 980 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121744_fcf37921-4351-4368-95ee-b5be2592d89a-dag_1608659125567_0008_195.log
> lrwx-- 1 hive hadoop 64 Dec 24 12:08 979 ->
> /hadoop/yarn/log/application_1608659125567_0006/container_e04_1608659125567_0006_01_02/hive_20201224121837_e80c0024-f6bc-4b3c-85ed-5c0c85c55787-dag_1608659125567_0008_199.log
>
[jira] [Resolved] (HIVE-27206) Backport of HIVE-20179 Some Tez jar-s are not on classpath so HS2 keeps too long to start
[ https://issues.apache.org/jira/browse/HIVE-27206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27206. - Fix Version/s: 3.2.0 Resolution: Fixed > Backport of HIVE-20179 Some Tez jar-s are not on classpath so HS2 keeps too > long to start > - > > Key: HIVE-27206 > URL: https://issues.apache.org/jira/browse/HIVE-27206 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > HIVE-20179 was already part of Hive 3.1.3 release so it makes sense to > backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27206) Backport of HIVE-20179 Some Tez jar-s are not on classpath so HS2 keeps too long to start
[ https://issues.apache.org/jira/browse/HIVE-27206?focusedWorklogId=855681=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855681 ] ASF GitHub Bot logged work on HIVE-27206: - Author: ASF GitHub Bot Created on: 10/Apr/23 04:06 Start Date: 10/Apr/23 04:06 Worklog Time Spent: 10m Work Description: sankarh merged PR #4182: URL: https://github.com/apache/hive/pull/4182 Issue Time Tracking --- Worklog Id: (was: 855681) Time Spent: 1h 10m (was: 1h) > Backport of HIVE-20179 Some Tez jar-s are not on classpath so HS2 keeps too > long to start > - > > Key: HIVE-27206 > URL: https://issues.apache.org/jira/browse/HIVE-27206 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > HIVE-20179 was already part of Hive 3.1.3 release so it makes sense to > backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-20179) Some Tez jar-s are not on classpath so HS2 keeps too long to start
[
https://issues.apache.org/jira/browse/HIVE-20179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sankar Hariappan updated HIVE-20179:
Fix Version/s: 3.2.0
> Some Tez jar-s are not on classpath so HS2 keeps too long to start
> --
>
> Key: HIVE-20179
> URL: https://issues.apache.org/jira/browse/HIVE-20179
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
>Affects Versions: 4.0.0
>Reporter: Peter Vary
>Assignee: Peter Vary
>Priority: Major
> Labels: release-3.1.3
> Fix For: 3.2.0, 4.0.0-alpha-1
>
> Attachments: HIVE-20179.2.patch, HIVE-20179.patch
>
>
> aideWhen trying to start HS2 in IDEA without any changes in the pom the
> following exception is thrown:
> {code}
> java.lang.NoClassDefFoundError: org/apache/tez/dag/api/TezConfiguration
> at
> org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolSession$AbstractTriggerValidator.startTriggerValidator(TezSessionPoolSession.java:74)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.initTriggers(TezSessionPoolManager.java:207)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.startPool(TezSessionPoolManager.java:114)
> at
> org.apache.hive.service.server.HiveServer2.initAndStartTezSessionPoolManager(HiveServer2.java:841)
> at
> org.apache.hive.service.server.HiveServer2.startOrReconnectTezSessions(HiveServer2.java:824)
> at org.apache.hive.service.server.HiveServer2.start(HiveServer2.java:746)
> at
> org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:1039)
> at
> org.apache.hive.service.server.HiveServer2.access$1600(HiveServer2.java:140)
> at
> org.apache.hive.service.server.HiveServer2$StartOptionExecutor.execute(HiveServer2.java:1307)
> at org.apache.hive.service.server.HiveServer2.main(HiveServer2.java:1151)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.tez.dag.api.TezConfiguration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 10 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-22033) HiveServer2: fix delegation token renewal
[ https://issues.apache.org/jira/browse/HIVE-22033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-22033: Fix Version/s: 3.2.0 > HiveServer2: fix delegation token renewal > - > > Key: HIVE-22033 > URL: https://issues.apache.org/jira/browse/HIVE-22033 > Project: Hive > Issue Type: Bug >Affects Versions: 2.3.5 >Reporter: Ion Alberdi >Assignee: Ion Alberdi >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0, 4.0.0-alpha-1 > > Attachments: HIVE-22033.2.patch, HIVE-22033.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Hello, the issue we faced (and a proposal for a fix) in our hive instances is > depicted at > [https://github.com/criteo-forks/hive/pull/24] > Reading the master branch of the project > > [https://github.com/apache/hive/blob/master/standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/security/TokenStoreDelegationTokenSecretManager.java#L147] > I think the same behavior is replicated there. > Long story short, *TokenStoreDelegationTokenSecretManager.renewToken*, does > not update the expiry date of a given token (as it does not get the updated > DelegationTokenInformation from *super.currentTokens*). > This makes any call to renewToken ineffective (the expiry date of the token > is not postponed). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-25665) Checkstyle LGPL files must not be in the release sources/binaries
[ https://issues.apache.org/jira/browse/HIVE-25665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-25665: Fix Version/s: 3.2.0 > Checkstyle LGPL files must not be in the release sources/binaries > - > > Key: HIVE-25665 > URL: https://issues.apache.org/jira/browse/HIVE-25665 > Project: Hive > Issue Type: Task > Components: Build Infrastructure >Affects Versions: 0.6.0 >Reporter: Stamatis Zampetakis >Assignee: Peter Vary >Priority: Blocker > Labels: pull-request-available > Fix For: 3.2.0, 4.0.0-alpha-1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > As discussed in the [dev > list|https://lists.apache.org/thread/r13e3236aa72a070b3267ed95f7cb3b45d3c4783fd4ca35f5376b1a35@%3cdev.hive.apache.org%3e] > LGPL files must not be present in the Apache released sources/binaries. > The following files must not be present in the release: > https://github.com/apache/hive/blob/6e152aa28bc5116bf9210f9deb0f95d2d73183f7/checkstyle/checkstyle-noframes-sorted.xsl > https://github.com/apache/hive/blob/6e152aa28bc5116bf9210f9deb0f95d2d73183f7/storage-api/checkstyle/checkstyle-noframes-sorted.xsl > https://github.com/apache/hive/blob/6e152aa28bc5116bf9210f9deb0f95d2d73183f7/standalone-metastore/checkstyle/checkstyle-noframes-sorted.xsl > There may be other checkstyle LGPL files in the repo. All these should either > be removed entirely from the repository or selectively excluded from the > release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27229) Backport of HIVE-25665: Checkstyle LGPL files must not be in the release sources/binaries
[ https://issues.apache.org/jira/browse/HIVE-27229?focusedWorklogId=855680=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855680 ] ASF GitHub Bot logged work on HIVE-27229: - Author: ASF GitHub Bot Created on: 10/Apr/23 04:00 Start Date: 10/Apr/23 04:00 Worklog Time Spent: 10m Work Description: sankarh merged PR #4208: URL: https://github.com/apache/hive/pull/4208 Issue Time Tracking --- Worklog Id: (was: 855680) Time Spent: 40m (was: 0.5h) > Backport of HIVE-25665: Checkstyle LGPL files must not be in the release > sources/binaries > - > > Key: HIVE-27229 > URL: https://issues.apache.org/jira/browse/HIVE-27229 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > HIVE-25665: Checkstyle LGPL files must not be in the release sources/binaries > - This was already present in branch-3.1 from where Hive-3.1.3 was cut, > therefore backporting this to branch-3 is necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27229) Backport of HIVE-25665: Checkstyle LGPL files must not be in the release sources/binaries
[ https://issues.apache.org/jira/browse/HIVE-27229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27229. - Fix Version/s: 3.2.0 Resolution: Fixed > Backport of HIVE-25665: Checkstyle LGPL files must not be in the release > sources/binaries > - > > Key: HIVE-27229 > URL: https://issues.apache.org/jira/browse/HIVE-27229 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Time Spent: 40m > Remaining Estimate: 0h > > HIVE-25665: Checkstyle LGPL files must not be in the release sources/binaries > - This was already present in branch-3.1 from where Hive-3.1.3 was cut, > therefore backporting this to branch-3 is necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27230) Backport of HIVE-22033 and HIVE-26522 to branch-3
[ https://issues.apache.org/jira/browse/HIVE-27230?focusedWorklogId=855678=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855678 ] ASF GitHub Bot logged work on HIVE-27230: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:56 Start Date: 10/Apr/23 03:56 Worklog Time Spent: 10m Work Description: sankarh merged PR #4209: URL: https://github.com/apache/hive/pull/4209 Issue Time Tracking --- Worklog Id: (was: 855678) Time Spent: 40m (was: 0.5h) > Backport of HIVE-22033 and HIVE-26522 to branch-3 > - > > Key: HIVE-27230 > URL: https://issues.apache.org/jira/browse/HIVE-27230 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > HIVE-26522: Backport of HIVE-22033 and HIVE-26522 to branch-3 - This commit > was already present in branch-3.1 so it is necessary to backport this to > branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27230) Backport of HIVE-22033 and HIVE-26522 to branch-3
[ https://issues.apache.org/jira/browse/HIVE-27230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27230. - Fix Version/s: 3.2.0 Target Version/s: 3.2.0 Resolution: Fixed > Backport of HIVE-22033 and HIVE-26522 to branch-3 > - > > Key: HIVE-27230 > URL: https://issues.apache.org/jira/browse/HIVE-27230 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Time Spent: 40m > Remaining Estimate: 0h > > HIVE-26522: Backport of HIVE-22033 and HIVE-26522 to branch-3 - This commit > was already present in branch-3.1 so it is necessary to backport this to > branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27238) Avoid Calcite Code generation for RelMetaDataProvider on every query
[ https://issues.apache.org/jira/browse/HIVE-27238?focusedWorklogId=855676=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855676 ] ASF GitHub Bot logged work on HIVE-27238: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:53 Start Date: 10/Apr/23 03:53 Worklog Time Spent: 10m Work Description: sonarcloud[bot] commented on PR #4212: URL: https://github.com/apache/hive/pull/4212#issuecomment-1501359074 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_hive=4212) [](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4212=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4212=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4212=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=CODE_SMELL) [5 Code Smells](https://sonarcloud.io/project/issues?id=apache_hive=4212=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_hive=4212=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_hive=4212=duplicated_lines_density=list) No Duplication information Issue Time Tracking --- Worklog Id: (was: 855676) Time Spent: 20m (was: 10m) > Avoid Calcite Code generation for RelMetaDataProvider on every query > > > Key: HIVE-27238 > URL: https://issues.apache.org/jira/browse/HIVE-27238 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Steve Carlin >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > In CalcitePlanner, we are instantiating a new CachingRelMetadataProvider on > every query. Within the Calcite code, they keep the provider key to prevent > a new MetadataHandler class from being created. But by generating a new > provider, the cache never gets a hit so we keep instantiating new > MetadataHandlers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27230) Backport of HIVE-22033 and HIVE-26522 to branch-3
[ https://issues.apache.org/jira/browse/HIVE-27230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-27230: Description: HIVE-26522: Backport of HIVE-22033 and HIVE-26522 to branch-3 - This commit was already present in branch-3.1 so it is necessary to backport this to branch-3 (was: HIVE-26522: Backport of HIVE-22033 and HIVE-26522 to branch-3.1 - This commit was already present in branch-3.1 so it is necessary to backport this to branch-3) > Backport of HIVE-22033 and HIVE-26522 to branch-3 > - > > Key: HIVE-27230 > URL: https://issues.apache.org/jira/browse/HIVE-27230 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-26522: Backport of HIVE-22033 and HIVE-26522 to branch-3 - This commit > was already present in branch-3.1 so it is necessary to backport this to > branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27231) Backport of HIVE-26530: HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple queryIds
[ https://issues.apache.org/jira/browse/HIVE-27231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27231. - Fix Version/s: 3.2.0 Resolution: Fixed > Backport of HIVE-26530: HS2 OOM-OperationManager.queryIdOperation does not > properly clean up multiple queryIds > -- > > Key: HIVE-27231 > URL: https://issues.apache.org/jira/browse/HIVE-27231 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This commit was present in branch-3.1 (Hive-3.1.3 release) so it is necessary > to backport this change to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27231) Backport of HIVE-26530: HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple queryIds
[ https://issues.apache.org/jira/browse/HIVE-27231?focusedWorklogId=855675=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855675 ] ASF GitHub Bot logged work on HIVE-27231: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:39 Start Date: 10/Apr/23 03:39 Worklog Time Spent: 10m Work Description: sankarh merged PR #4210: URL: https://github.com/apache/hive/pull/4210 Issue Time Tracking --- Worklog Id: (was: 855675) Time Spent: 40m (was: 0.5h) > Backport of HIVE-26530: HS2 OOM-OperationManager.queryIdOperation does not > properly clean up multiple queryIds > -- > > Key: HIVE-27231 > URL: https://issues.apache.org/jira/browse/HIVE-27231 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > This commit was present in branch-3.1 (Hive-3.1.3 release) so it is necessary > to backport this change to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-26530) HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple queryIds
[ https://issues.apache.org/jira/browse/HIVE-26530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-26530: Fix Version/s: 3.2.0 (was: 3.1.3) > HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple > queryIds > -- > > Key: HIVE-26530 > URL: https://issues.apache.org/jira/browse/HIVE-26530 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Affects Versions: 3.1.2 >Reporter: Fachuan Bai >Assignee: Fachuan Bai >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Original Estimate: 168h > Time Spent: 0.5h > Remaining Estimate: 167.5h > > Version: Hive 3.1.2 > I used Airflow to execute the Hive SQL while the Hive Server2 will OOM. > I found the same issue: https://issues.apache.org/jira/browse/HIVE-22275 > But it is only fixed on 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-26530) HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple queryIds
[ https://issues.apache.org/jira/browse/HIVE-26530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-26530: Fix Version/s: 3.1.3 (was: 3.2.0) > HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple > queryIds > -- > > Key: HIVE-26530 > URL: https://issues.apache.org/jira/browse/HIVE-26530 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Affects Versions: 3.1.2 >Reporter: Fachuan Bai >Assignee: Fachuan Bai >Priority: Major > Labels: pull-request-available > Fix For: 3.1.3 > > Original Estimate: 168h > Time Spent: 0.5h > Remaining Estimate: 167.5h > > Version: Hive 3.1.2 > I used Airflow to execute the Hive SQL while the Hive Server2 will OOM. > I found the same issue: https://issues.apache.org/jira/browse/HIVE-22275 > But it is only fixed on 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27216) Upgrade postgresql to 42.5.1 from 9.x
[ https://issues.apache.org/jira/browse/HIVE-27216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27216. - Fix Version/s: 3.2.0 Resolution: Fixed > Upgrade postgresql to 42.5.1 from 9.x > - > > Key: HIVE-27216 > URL: https://issues.apache.org/jira/browse/HIVE-27216 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > This ticket involves partial cherry pick of #HIVE-23965 and complete cherry > picks of HIVE-26253 and HIVE-26914 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27230) Backport of HIVE-22033 and HIVE-26522 to branch-3
[ https://issues.apache.org/jira/browse/HIVE-27230?focusedWorklogId=855673=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855673 ] ASF GitHub Bot logged work on HIVE-27230: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:16 Start Date: 10/Apr/23 03:16 Worklog Time Spent: 10m Work Description: amanraj2520 commented on PR #4209: URL: https://github.com/apache/hive/pull/4209#issuecomment-1501340941 @vihangk1 Can you please review and merge this Issue Time Tracking --- Worklog Id: (was: 855673) Time Spent: 0.5h (was: 20m) > Backport of HIVE-22033 and HIVE-26522 to branch-3 > - > > Key: HIVE-27230 > URL: https://issues.apache.org/jira/browse/HIVE-27230 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-26522: Backport of HIVE-22033 and HIVE-26522 to branch-3.1 - This commit > was already present in branch-3.1 so it is necessary to backport this to > branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27231) Backport of HIVE-26530: HS2 OOM-OperationManager.queryIdOperation does not properly clean up multiple queryIds
[ https://issues.apache.org/jira/browse/HIVE-27231?focusedWorklogId=855674=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855674 ] ASF GitHub Bot logged work on HIVE-27231: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:16 Start Date: 10/Apr/23 03:16 Worklog Time Spent: 10m Work Description: amanraj2520 commented on PR #4210: URL: https://github.com/apache/hive/pull/4210#issuecomment-1501341135 @vihangk1 Can you please review and merge this Issue Time Tracking --- Worklog Id: (was: 855674) Time Spent: 0.5h (was: 20m) > Backport of HIVE-26530: HS2 OOM-OperationManager.queryIdOperation does not > properly clean up multiple queryIds > -- > > Key: HIVE-27231 > URL: https://issues.apache.org/jira/browse/HIVE-27231 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > This commit was present in branch-3.1 (Hive-3.1.3 release) so it is necessary > to backport this change to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27206) Backport of HIVE-20179 Some Tez jar-s are not on classpath so HS2 keeps too long to start
[ https://issues.apache.org/jira/browse/HIVE-27206?focusedWorklogId=855670=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855670 ] ASF GitHub Bot logged work on HIVE-27206: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:15 Start Date: 10/Apr/23 03:15 Worklog Time Spent: 10m Work Description: amanraj2520 commented on PR #4182: URL: https://github.com/apache/hive/pull/4182#issuecomment-1501340546 @vihangk1 Can you please merge this. Issue Time Tracking --- Worklog Id: (was: 855670) Time Spent: 1h (was: 50m) > Backport of HIVE-20179 Some Tez jar-s are not on classpath so HS2 keeps too > long to start > - > > Key: HIVE-27206 > URL: https://issues.apache.org/jira/browse/HIVE-27206 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > HIVE-20179 was already part of Hive 3.1.3 release so it makes sense to > backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27229) Backport of HIVE-25665: Checkstyle LGPL files must not be in the release sources/binaries
[ https://issues.apache.org/jira/browse/HIVE-27229?focusedWorklogId=855672=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855672 ] ASF GitHub Bot logged work on HIVE-27229: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:15 Start Date: 10/Apr/23 03:15 Worklog Time Spent: 10m Work Description: amanraj2520 commented on PR #4208: URL: https://github.com/apache/hive/pull/4208#issuecomment-1501340775 @vihangk1 Can you please review and merge this Issue Time Tracking --- Worklog Id: (was: 855672) Time Spent: 0.5h (was: 20m) > Backport of HIVE-25665: Checkstyle LGPL files must not be in the release > sources/binaries > - > > Key: HIVE-27229 > URL: https://issues.apache.org/jira/browse/HIVE-27229 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-25665: Checkstyle LGPL files must not be in the release sources/binaries > - This was already present in branch-3.1 from where Hive-3.1.3 was cut, > therefore backporting this to branch-3 is necessary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27238) Avoid Calcite Code generation for RelMetaDataProvider on every query
[ https://issues.apache.org/jira/browse/HIVE-27238?focusedWorklogId=855669=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855669 ] ASF GitHub Bot logged work on HIVE-27238: - Author: ASF GitHub Bot Created on: 10/Apr/23 03:01 Start Date: 10/Apr/23 03:01 Worklog Time Spent: 10m Work Description: scarlin-cloudera opened a new pull request, #4212: URL: https://github.com/apache/hive/pull/4212 …y query In the current code base, a new CachingRelMetadataProvider is created on every query. This causes a cache miss within JaninoRelMetadataProvider, which stores the provider in the key. As a result, a new MetadataHandler is created multiple times in every query, which causes code generation and is a small hit on performance This commit caches HiveDefaultRelMetadataProviders globally which stores a RelMetadataProvider that can be reused. Ultimately, this class could most likely be removed as well, but this commit limits the scope of the change in a first pass. ### What changes were proposed in this pull request? Stated in commit message ### Why are the changes needed? This will help performance and possibly have a smaller memory footprint. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? This doesn't introduce new functionality, so current regression tests should be good. I ran this through the debugger and made sure the Calcite JaninoMetadataProvider.load3 method was not called after the first query was called with the same conf variables. Issue Time Tracking --- Worklog Id: (was: 855669) Remaining Estimate: 0h Time Spent: 10m > Avoid Calcite Code generation for RelMetaDataProvider on every query > > > Key: HIVE-27238 > URL: https://issues.apache.org/jira/browse/HIVE-27238 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Steve Carlin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In CalcitePlanner, we are instantiating a new CachingRelMetadataProvider on > every query. Within the Calcite code, they keep the provider key to prevent > a new MetadataHandler class from being created. But by generating a new > provider, the cache never gets a hit so we keep instantiating new > MetadataHandlers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27238) Avoid Calcite Code generation for RelMetaDataProvider on every query
[ https://issues.apache.org/jira/browse/HIVE-27238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27238: -- Labels: pull-request-available (was: ) > Avoid Calcite Code generation for RelMetaDataProvider on every query > > > Key: HIVE-27238 > URL: https://issues.apache.org/jira/browse/HIVE-27238 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Steve Carlin >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > In CalcitePlanner, we are instantiating a new CachingRelMetadataProvider on > every query. Within the Calcite code, they keep the provider key to prevent > a new MetadataHandler class from being created. But by generating a new > provider, the cache never gets a hit so we keep instantiating new > MetadataHandlers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27238) Avoid Calcite Code generation for RelMetaDataProvider on every query
Steve Carlin created HIVE-27238: --- Summary: Avoid Calcite Code generation for RelMetaDataProvider on every query Key: HIVE-27238 URL: https://issues.apache.org/jira/browse/HIVE-27238 Project: Hive Issue Type: Improvement Components: HiveServer2 Reporter: Steve Carlin In CalcitePlanner, we are instantiating a new CachingRelMetadataProvider on every query. Within the Calcite code, they keep the provider key to prevent a new MetadataHandler class from being created. But by generating a new provider, the cache never gets a hit so we keep instantiating new MetadataHandlers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27052) Backport HIVE-26080: Upgrade accumulo-core to 1.10.1 in branch-3
[ https://issues.apache.org/jira/browse/HIVE-27052?focusedWorklogId=855662=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855662 ] ASF GitHub Bot logged work on HIVE-27052: - Author: ASF GitHub Bot Created on: 10/Apr/23 00:19 Start Date: 10/Apr/23 00:19 Worklog Time Spent: 10m Work Description: github-actions[bot] commented on PR #4034: URL: https://github.com/apache/hive/pull/4034#issuecomment-150125 This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Feel free to reach out on the d...@hive.apache.org list if the patch is in need of reviews. Issue Time Tracking --- Worklog Id: (was: 855662) Time Spent: 20m (was: 10m) > Backport HIVE-26080: Upgrade accumulo-core to 1.10.1 in branch-3 > > > Key: HIVE-27052 > URL: https://issues.apache.org/jira/browse/HIVE-27052 > Project: Hive > Issue Type: Improvement >Reporter: Raghav Aggarwal >Assignee: Raghav Aggarwal >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27173) Add method for Spark to be able to trigger DML events
[ https://issues.apache.org/jira/browse/HIVE-27173?focusedWorklogId=855653=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855653 ] ASF GitHub Bot logged work on HIVE-27173: - Author: ASF GitHub Bot Created on: 09/Apr/23 12:50 Start Date: 09/Apr/23 12:50 Worklog Time Spent: 10m Work Description: sonarcloud[bot] commented on PR #4201: URL: https://github.com/apache/hive/pull/4201#issuecomment-1501122513 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_hive=4201) [](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4201=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4201=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4201=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=CODE_SMELL) [6 Code Smells](https://sonarcloud.io/project/issues?id=apache_hive=4201=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_hive=4201=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_hive=4201=duplicated_lines_density=list) No Duplication information Issue Time Tracking --- Worklog Id: (was: 855653) Time Spent: 0.5h (was: 20m) > Add method for Spark to be able to trigger DML events > - > > Key: HIVE-27173 > URL: https://issues.apache.org/jira/browse/HIVE-27173 > Project: Hive > Issue Type: Improvement >Reporter: Naveen Gangam >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Spark currently uses Hive.java from Hive as a convenient way to hide from the > having to deal with HMS Client and the thrift objects. Currently, Hive has > support for DML events (being able to generate events on DML operations but > does not expose a public method to do so). It has a private method that takes > in Hive objects like Table etc. Would be nice if we can have something with > more primitive datatypes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HIVE-27232) Backport of HIVE-24694: Early connection close to release server resources during creating
[ https://issues.apache.org/jira/browse/HIVE-27232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709960#comment-17709960 ] Zhihua Deng edited comment on HIVE-27232 at 4/9/23 11:06 AM: - Fix has been merged. Thank you [~amanraj2520] for the PR! was (Author: dengzh): PR has been merged. Thank you [~amanraj2520] for the PR! > Backport of HIVE-24694: Early connection close to release server resources > during creating > -- > > Key: HIVE-27232 > URL: https://issues.apache.org/jira/browse/HIVE-27232 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-26743: backport HIVE-24694: Early connection close to release server > resources during creating - This commit was already present in 3.1.3 Hive > release so it is necessary to backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27232) Backport of HIVE-24694: Early connection close to release server resources during creating
[ https://issues.apache.org/jira/browse/HIVE-27232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihua Deng resolved HIVE-27232. Resolution: Fixed > Backport of HIVE-24694: Early connection close to release server resources > during creating > -- > > Key: HIVE-27232 > URL: https://issues.apache.org/jira/browse/HIVE-27232 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-26743: backport HIVE-24694: Early connection close to release server > resources during creating - This commit was already present in 3.1.3 Hive > release so it is necessary to backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-27232) Backport of HIVE-24694: Early connection close to release server resources during creating
[ https://issues.apache.org/jira/browse/HIVE-27232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709960#comment-17709960 ] Zhihua Deng commented on HIVE-27232: PR has been merged. Thank you [~amanraj2520] for the PR! > Backport of HIVE-24694: Early connection close to release server resources > during creating > -- > > Key: HIVE-27232 > URL: https://issues.apache.org/jira/browse/HIVE-27232 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-26743: backport HIVE-24694: Early connection close to release server > resources during creating - This commit was already present in 3.1.3 Hive > release so it is necessary to backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27232) Backport of HIVE-24694: Early connection close to release server resources during creating
[ https://issues.apache.org/jira/browse/HIVE-27232?focusedWorklogId=855652=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855652 ] ASF GitHub Bot logged work on HIVE-27232: - Author: ASF GitHub Bot Created on: 09/Apr/23 11:02 Start Date: 09/Apr/23 11:02 Worklog Time Spent: 10m Work Description: dengzhhu653 merged PR #4211: URL: https://github.com/apache/hive/pull/4211 Issue Time Tracking --- Worklog Id: (was: 855652) Time Spent: 0.5h (was: 20m) > Backport of HIVE-24694: Early connection close to release server resources > during creating > -- > > Key: HIVE-27232 > URL: https://issues.apache.org/jira/browse/HIVE-27232 > Project: Hive > Issue Type: Sub-task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > HIVE-26743: backport HIVE-24694: Early connection close to release server > resources during creating - This commit was already present in 3.1.3 Hive > release so it is necessary to backport this to branch-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27233) Iceberg: BRANCH implementation on hive side
[ https://issues.apache.org/jira/browse/HIVE-27233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao updated HIVE-27233: -- Issue Type: New Feature (was: Improvement) > Iceberg: BRANCH implementation on hive side > > > Key: HIVE-27233 > URL: https://issues.apache.org/jira/browse/HIVE-27233 > Project: Hive > Issue Type: New Feature > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > > This can be a umbrella ticket to track branch implementation on hive side. > We can refer to design doc which has been reviewed in iceberg community: > https://docs.google.com/document/d/1tbATFPrKF3vNlzkgZQdaW8CAJmbjvryfrlg6C2Ci_aA/edit#heading=h.gflazgojtfmi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (HIVE-27197) Iceberg: Support Iceberg version travel by reference name
[ https://issues.apache.org/jira/browse/HIVE-27197?focusedWorklogId=855645=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855645 ] ASF GitHub Bot logged work on HIVE-27197: - Author: ASF GitHub Bot Created on: 09/Apr/23 09:40 Start Date: 09/Apr/23 09:40 Worklog Time Spent: 10m Work Description: sonarcloud[bot] commented on PR #4173: URL: https://github.com/apache/hive/pull/4173#issuecomment-1501087984 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_hive=4173) [](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4173=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4173=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_hive=4173=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=apache_hive=4173=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_hive=4173=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_hive=4173=duplicated_lines_density=list) No Duplication information Issue Time Tracking --- Worklog Id: (was: 855645) Time Spent: 50m (was: 40m) > Iceberg: Support Iceberg version travel by reference name > --- > > Key: HIVE-27197 > URL: https://issues.apache.org/jira/browse/HIVE-27197 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > This ticket is inspired by https://github.com/apache/iceberg/pull/6575 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27236) Iceberg: DROP BRANCH SQL implementation
[ https://issues.apache.org/jira/browse/HIVE-27236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao reassigned HIVE-27236: - Assignee: zhangbutao > Iceberg: DROP BRANCH SQL implementation > --- > > Key: HIVE-27236 > URL: https://issues.apache.org/jira/browse/HIVE-27236 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27237) Iceberg: DROP TAG SQL implementation
zhangbutao created HIVE-27237: - Summary: Iceberg: DROP TAG SQL implementation Key: HIVE-27237 URL: https://issues.apache.org/jira/browse/HIVE-27237 Project: Hive Issue Type: Sub-task Components: Iceberg integration Reporter: zhangbutao -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27237) Iceberg: DROP TAG SQL implementation
[ https://issues.apache.org/jira/browse/HIVE-27237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao reassigned HIVE-27237: - Assignee: zhangbutao > Iceberg: DROP TAG SQL implementation > > > Key: HIVE-27237 > URL: https://issues.apache.org/jira/browse/HIVE-27237 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27236) Iceberg: DROP BRANCH SQL implementation
zhangbutao created HIVE-27236: - Summary: Iceberg: DROP BRANCH SQL implementation Key: HIVE-27236 URL: https://issues.apache.org/jira/browse/HIVE-27236 Project: Hive Issue Type: Sub-task Components: Iceberg integration Reporter: zhangbutao -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27235) Iceberg: CREATE TAG SQL implementation
[ https://issues.apache.org/jira/browse/HIVE-27235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao reassigned HIVE-27235: - Assignee: zhangbutao > Iceberg: CREATE TAG SQL implementation > -- > > Key: HIVE-27235 > URL: https://issues.apache.org/jira/browse/HIVE-27235 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27235) Iceberg: CREATE TAG SQL implementation
zhangbutao created HIVE-27235: - Summary: Iceberg: CREATE TAG SQL implementation Key: HIVE-27235 URL: https://issues.apache.org/jira/browse/HIVE-27235 Project: Hive Issue Type: Sub-task Components: Iceberg integration Reporter: zhangbutao -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27234) Iceberg: CREATE BRANCH SQL implementation
[ https://issues.apache.org/jira/browse/HIVE-27234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao updated HIVE-27234: -- Description: Maybe we can follow spark sql about branch ddl implementation [https://github.com/apache/iceberg/pull/6617] (was: Spark https://github.com/apache/iceberg/pull/6617) > Iceberg: CREATE BRANCH SQL implementation > -- > > Key: HIVE-27234 > URL: https://issues.apache.org/jira/browse/HIVE-27234 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > > Maybe we can follow spark sql about branch ddl implementation > [https://github.com/apache/iceberg/pull/6617] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27234) Iceberg: CREATE BRANCH SQL implementation
[ https://issues.apache.org/jira/browse/HIVE-27234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao updated HIVE-27234: -- Description: Spark https://github.com/apache/iceberg/pull/6617 > Iceberg: CREATE BRANCH SQL implementation > -- > > Key: HIVE-27234 > URL: https://issues.apache.org/jira/browse/HIVE-27234 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > > Spark https://github.com/apache/iceberg/pull/6617 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27234) Iceberg: CREATE BRANCH SQL implementation
zhangbutao created HIVE-27234: - Summary: Iceberg: CREATE BRANCH SQL implementation Key: HIVE-27234 URL: https://issues.apache.org/jira/browse/HIVE-27234 Project: Hive Issue Type: Sub-task Components: Iceberg integration Reporter: zhangbutao -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27234) Iceberg: CREATE BRANCH SQL implementation
[ https://issues.apache.org/jira/browse/HIVE-27234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao reassigned HIVE-27234: - Assignee: zhangbutao > Iceberg: CREATE BRANCH SQL implementation > -- > > Key: HIVE-27234 > URL: https://issues.apache.org/jira/browse/HIVE-27234 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27197) Iceberg: Support Iceberg version travel by reference name
[ https://issues.apache.org/jira/browse/HIVE-27197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao updated HIVE-27197: -- Parent: HIVE-27233 Issue Type: Sub-task (was: Improvement) > Iceberg: Support Iceberg version travel by reference name > --- > > Key: HIVE-27197 > URL: https://issues.apache.org/jira/browse/HIVE-27197 > Project: Hive > Issue Type: Sub-task > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > This ticket is inspired by https://github.com/apache/iceberg/pull/6575 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27233) Iceberg: BRANCH implementation on hive side
[ https://issues.apache.org/jira/browse/HIVE-27233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangbutao reassigned HIVE-27233: - Assignee: zhangbutao > Iceberg: BRANCH implementation on hive side > > > Key: HIVE-27233 > URL: https://issues.apache.org/jira/browse/HIVE-27233 > Project: Hive > Issue Type: Improvement > Components: Iceberg integration >Reporter: zhangbutao >Assignee: zhangbutao >Priority: Major > > This can be a umbrella ticket to track branch implementation on hive side. > We can refer to design doc which has been reviewed in iceberg community: > https://docs.google.com/document/d/1tbATFPrKF3vNlzkgZQdaW8CAJmbjvryfrlg6C2Ci_aA/edit#heading=h.gflazgojtfmi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27233) Iceberg: BRANCH implementation on hive side
zhangbutao created HIVE-27233: - Summary: Iceberg: BRANCH implementation on hive side Key: HIVE-27233 URL: https://issues.apache.org/jira/browse/HIVE-27233 Project: Hive Issue Type: Improvement Components: Iceberg integration Reporter: zhangbutao This can be a umbrella ticket to track branch implementation on hive side. We can refer to design doc which has been reviewed in iceberg community: https://docs.google.com/document/d/1tbATFPrKF3vNlzkgZQdaW8CAJmbjvryfrlg6C2Ci_aA/edit#heading=h.gflazgojtfmi -- This message was sent by Atlassian Jira (v8.20.10#820010)
