[jira] [Updated] (HIVE-28712) Fix error wrt maxParts in partition logs
[ https://issues.apache.org/jira/browse/HIVE-28712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-28712: -- Labels: pull-request-available (was: ) > Fix error wrt maxParts in partition logs > > > Key: HIVE-28712 > URL: https://issues.apache.org/jira/browse/HIVE-28712 > Project: Hive > Issue Type: Bug >Reporter: Simran Arora >Assignee: Simran Arora >Priority: Major > Labels: pull-request-available > > Current partition logs display max partitions = -1, which is the default > value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is > not displayed, instead -1 continues to be logged. > This issue is to fix this error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28712) Fix error wrt maxParts in partition logs
[ https://issues.apache.org/jira/browse/HIVE-28712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simran Arora updated HIVE-28712: Description: Current partition logs display max partitions = -1, which is the default value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is not displayed, instead -1 continues to be logged. This issue is to fix this error. was: Current partition logs display max partitions = -1, which is the default value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is not displayed, instead -1 continues to be logged. This issue is to fix this error. !https://github.trusted.visa.com/storage/user/1251/files/19197b80-b4d0-4053-869a-7557cb10d51d?token=LDPUZYSFWMIVO3H4PI3HRCIT2! > Fix error wrt maxParts in partition logs > > > Key: HIVE-28712 > URL: https://issues.apache.org/jira/browse/HIVE-28712 > Project: Hive > Issue Type: Bug >Reporter: Simran Arora >Assignee: Simran Arora >Priority: Major > > Current partition logs display max partitions = -1, which is the default > value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is > not displayed, instead -1 continues to be logged. > This issue is to fix this error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28712) Fix error wrt maxParts in partition logs
[ https://issues.apache.org/jira/browse/HIVE-28712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simran Arora updated HIVE-28712: Description: Current partition logs display max partitions = -1, which is the default value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is not displayed, instead -1 continues to be logged. This issue is to fix this error. !https://github.trusted.visa.com/storage/user/1251/files/19197b80-b4d0-4053-869a-7557cb10d51d?token=LDPUZYSFWMIVO3H4PI3HRCIT2! was: Current partition logs display max partitions = -1, which is the default value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is not displayed, instead -1 continues to be logged. This issue is to fix this error. > Fix error wrt maxParts in partition logs > > > Key: HIVE-28712 > URL: https://issues.apache.org/jira/browse/HIVE-28712 > Project: Hive > Issue Type: Bug >Reporter: Simran Arora >Assignee: Simran Arora >Priority: Major > > Current partition logs display max partitions = -1, which is the default > value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is > not displayed, instead -1 continues to be logged. > This issue is to fix this error. > > !https://github.trusted.visa.com/storage/user/1251/files/19197b80-b4d0-4053-869a-7557cb10d51d?token=LDPUZYSFWMIVO3H4PI3HRCIT2! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28712) Fix error wrt maxParts in partition logs
[ https://issues.apache.org/jira/browse/HIVE-28712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simran Arora updated HIVE-28712: Description: Current partition logs display max partitions = -1, which is the default value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is not displayed, instead -1 continues to be logged. This issue is to fix this error. > Fix error wrt maxParts in partition logs > > > Key: HIVE-28712 > URL: https://issues.apache.org/jira/browse/HIVE-28712 > Project: Hive > Issue Type: Bug >Reporter: Simran Arora >Assignee: Simran Arora >Priority: Major > > Current partition logs display max partitions = -1, which is the default > value. But on changing the value of LIMIT_PARTITION_REQUEST, the set value is > not displayed, instead -1 continues to be logged. > This issue is to fix this error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
