[jira] [Updated] (HIVE-26211) "hive.server2.webui.max.historic.queries" should be avoided to be set too large, otherwise it will cause blocking

2022-11-06 Thread ECFuzz (Jira)
[ https://issues.apache.org/jira/browse/HIVE-26211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HIVE-26211: -- Priority: Blocker (was: Major) > "hive.server2.webui.max.historic.queries" should be avoided to be set too >

[jira] [Updated] (HIVE-26211) "hive.server2.webui.max.historic.queries" should be avoided to be set too large, otherwise it will cause blocking

2022-11-06 Thread ECFuzz (Jira)
[ https://issues.apache.org/jira/browse/HIVE-26211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HIVE-26211: -- Component/s: Clients > "hive.server2.webui.max.historic.queries" should be avoided to be set too > large,

[jira] [Updated] (HIVE-26213) "hive.limit.pushdown.memory.usage" better not be equal to 1.0, otherwise it will raise an error

2022-11-06 Thread ECFuzz (Jira)
[ https://issues.apache.org/jira/browse/HIVE-26213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ECFuzz updated HIVE-26213: -- Component/s: Documentation > "hive.limit.pushdown.memory.usage" better not be equal to 1.0, otherwise it >