[jira] [Resolved] (HIVE-27219) Backport of HIVE-25616: Hive-24741 backport to 3.1
[ https://issues.apache.org/jira/browse/HIVE-27219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27219. - Resolution: Fixed > Backport of HIVE-25616: Hive-24741 backport to 3.1 > -- > > Key: HIVE-27219 > URL: https://issues.apache.org/jira/browse/HIVE-27219 > Project: Hive > Issue Type: Sub-task >Reporter: Apoorva Aggarwal >Assignee: Apoorva Aggarwal >Priority: Major > Labels: hive-3.2.0-must, pull-request-available > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27381) Upgrade Arrow to 7.0.0
[ https://issues.apache.org/jira/browse/HIVE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27381: -- Labels: pull-request-available (was: ) > Upgrade Arrow to 7.0.0 > -- > > Key: HIVE-27381 > URL: https://issues.apache.org/jira/browse/HIVE-27381 > Project: Hive > Issue Type: Task >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27381) Upgrade Arrow to 7.0.0
Aman Raj created HIVE-27381: --- Summary: Upgrade Arrow to 7.0.0 Key: HIVE-27381 URL: https://issues.apache.org/jira/browse/HIVE-27381 Project: Hive Issue Type: Task Reporter: Aman Raj Assignee: Aman Raj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27375) SharedWorkOptimizer assigns a common cache key to MapJoin operators that should not share MapJoin tables
[ https://issues.apache.org/jira/browse/HIVE-27375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sungwoo Park reassigned HIVE-27375: --- Assignee: Seonggon Namgung > SharedWorkOptimizer assigns a common cache key to MapJoin operators that > should not share MapJoin tables > > > Key: HIVE-27375 > URL: https://issues.apache.org/jira/browse/HIVE-27375 > Project: Hive > Issue Type: Bug >Reporter: Sungwoo Park >Assignee: Seonggon Namgung >Priority: Major > Labels: pull-request-available > > When hive.optimize.shared.work.mapjoin.cache.reuse is set to true, > SharedWorkOptimizer sometimes assigns a common cache key to MapJoin operators > that should not share MapJoin tables. This bug occurs only for MapJoin > operators with 3 or more parent operators. > Example: > MAPJOIN[575] (RS_83, GBY_66, RS_85) > MAPJOIN[585] (RS_212, RS_213, GBY_210) > In this example, both MAPJOIN[575] and MAPJOIN[585] have three parent > operators. The current implementation assigns a common cache key to > MAPJOIN[575] and MAPJOIN[585] because RS_83 are RS_212 are equivalent. > However, MAPJOIN[575] uses GBY_66 for its big table whereas MAPJOIN[585] uses > GBY_210 for its big table. As a result, the MapJoin table loaded by one > operator cannot be used by the other. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (HIVE-26978) Stale "Runtime stats" causes poor query planning
[ https://issues.apache.org/jira/browse/HIVE-26978 ] Zoltan Haindrich deleted comment on HIVE-26978: - was (Author: kgyrtkirk): have you restarted the HS2? the runtime stats are cached there; the metastore only stores them > Stale "Runtime stats" causes poor query planning > > > Key: HIVE-26978 > URL: https://issues.apache.org/jira/browse/HIVE-26978 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Rajesh Balamohan >Priority: Major > Labels: performance > Attachments: Screenshot 2023-01-24 at 10.23.16 AM.png > > > * Runtime stats can be stored in hiveserver or in metastore via > "hive.query.reexecution.stats.persist.scope". > * Though the table is dropped and recreated, it ends up showing old stats > via "RUNTIME" stats. Here is an example (note that the table is empty, but > gets datasize and numRows from RUNTIME stats) > * This causes suboptimal plan for "MERGE INTO" queries by creating > CUSTOM_EDGE instead of broadcast edge. > !Screenshot 2023-01-24 at 10.23.16 AM.png|width=2053,height=753! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-26978) Stale "Runtime stats" causes poor query planning
[ https://issues.apache.org/jira/browse/HIVE-26978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726585#comment-17726585 ] Zoltan Haindrich commented on HIVE-26978: - have you restarted the HS2? the runtime stats are cached there; the metastore only stores them > Stale "Runtime stats" causes poor query planning > > > Key: HIVE-26978 > URL: https://issues.apache.org/jira/browse/HIVE-26978 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Rajesh Balamohan >Priority: Major > Labels: performance > Attachments: Screenshot 2023-01-24 at 10.23.16 AM.png > > > * Runtime stats can be stored in hiveserver or in metastore via > "hive.query.reexecution.stats.persist.scope". > * Though the table is dropped and recreated, it ends up showing old stats > via "RUNTIME" stats. Here is an example (note that the table is empty, but > gets datasize and numRows from RUNTIME stats) > * This causes suboptimal plan for "MERGE INTO" queries by creating > CUSTOM_EDGE instead of broadcast edge. > !Screenshot 2023-01-24 at 10.23.16 AM.png|width=2053,height=753! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27380) Backport of HIVE-24751: Kill trigger in workload manager fails with "No privilege" exception when authorization is disabled.
Diksha created HIVE-27380: - Summary: Backport of HIVE-24751: Kill trigger in workload manager fails with "No privilege" exception when authorization is disabled. Key: HIVE-27380 URL: https://issues.apache.org/jira/browse/HIVE-27380 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-24751: Kill trigger in workload manager fails with "No privilege" exception when authorization is disabled. it is not checked whether authorization is enabled or not for Kill Query access. This causes Workload Manager thread to end up with No privilege Exception when trying to kill a query in an environment where authorization is disabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27375) SharedWorkOptimizer assigns a common cache key to MapJoin operators that should not share MapJoin tables
[ https://issues.apache.org/jira/browse/HIVE-27375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27375: -- Labels: pull-request-available (was: ) > SharedWorkOptimizer assigns a common cache key to MapJoin operators that > should not share MapJoin tables > > > Key: HIVE-27375 > URL: https://issues.apache.org/jira/browse/HIVE-27375 > Project: Hive > Issue Type: Bug >Reporter: Sungwoo Park >Priority: Major > Labels: pull-request-available > > When hive.optimize.shared.work.mapjoin.cache.reuse is set to true, > SharedWorkOptimizer sometimes assigns a common cache key to MapJoin operators > that should not share MapJoin tables. This bug occurs only for MapJoin > operators with 3 or more parent operators. > Example: > MAPJOIN[575] (RS_83, GBY_66, RS_85) > MAPJOIN[585] (RS_212, RS_213, GBY_210) > In this example, both MAPJOIN[575] and MAPJOIN[585] have three parent > operators. The current implementation assigns a common cache key to > MAPJOIN[575] and MAPJOIN[585] because RS_83 are RS_212 are equivalent. > However, MAPJOIN[575] uses GBY_66 for its big table whereas MAPJOIN[585] uses > GBY_210 for its big table. As a result, the MapJoin table loaded by one > operator cannot be used by the other. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27369) Replace log4j 1.x with reload4j
[ https://issues.apache.org/jira/browse/HIVE-27369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27369: -- Labels: pull-request-available (was: ) > Replace log4j 1.x with reload4j > --- > > Key: HIVE-27369 > URL: https://issues.apache.org/jira/browse/HIVE-27369 > Project: Hive > Issue Type: Task >Reporter: Devaspati Krishnatri >Assignee: Devaspati Krishnatri >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27379) Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state
[ https://issues.apache.org/jira/browse/HIVE-27379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27379: -- Labels: pull-request-available (was: ) > Backport of HIVE-22566: Drop table involved in materialized view leaves the > table in inconsistent state > --- > > Key: HIVE-27379 > URL: https://issues.apache.org/jira/browse/HIVE-27379 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: pull-request-available > > Backport of HIVE-22566: Drop table involved in materialized view leaves the > table in inconsistent state -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27379) Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state
Diksha created HIVE-27379: - Summary: Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state Key: HIVE-27379 URL: https://issues.apache.org/jira/browse/HIVE-27379 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27378) Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly
[ https://issues.apache.org/jira/browse/HIVE-27378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27378: -- Labels: pull-request-available (was: ) > Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing > correctly > -- > > Key: HIVE-27378 > URL: https://issues.apache.org/jira/browse/HIVE-27378 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: pull-request-available > > Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing > correctly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27378) Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly
Diksha created HIVE-27378: - Summary: Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly Key: HIVE-27378 URL: https://issues.apache.org/jira/browse/HIVE-27378 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27377) Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action
[ https://issues.apache.org/jira/browse/HIVE-27377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27377: -- Labels: pull-request-available (was: ) > Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics > after Kill Trigger action > --- > > Key: HIVE-27377 > URL: https://issues.apache.org/jira/browse/HIVE-27377 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: pull-request-available > > Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics > after Kill Trigger action -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27377) Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action
Diksha created HIVE-27377: - Summary: Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action Key: HIVE-27377 URL: https://issues.apache.org/jira/browse/HIVE-27377 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action -- This message was sent by Atlassian Jira (v8.20.10#820010)
