[jira] [Created] (HIVE-28235) Hive should honour heapsize set in hive-env
Anmol Sundaram created HIVE-28235: - Summary: Hive should honour heapsize set in hive-env Key: HIVE-28235 URL: https://issues.apache.org/jira/browse/HIVE-28235 Project: Hive Issue Type: Bug Reporter: Anmol Sundaram Assignee: Anmol Sundaram Hive processes do not honour the heap size set in hive-env. Right now, they only consider the value set in hadoop-env and ignore those set in hive-env. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-28235) Hive should honour heapsize set in hive-env
[ https://issues.apache.org/jira/browse/HIVE-28235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram reassigned HIVE-28235: - Assignee: (was: Anmol Sundaram) > Hive should honour heapsize set in hive-env > --- > > Key: HIVE-28235 > URL: https://issues.apache.org/jira/browse/HIVE-28235 > Project: Hive > Issue Type: Bug >Reporter: Anmol Sundaram >Priority: Major > > Hive processes do not honour the heap size set in hive-env. Right now, they > only consider the value set in hadoop-env and ignore those set in hive-env. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28043) Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3
[ https://issues.apache.org/jira/browse/HIVE-28043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28043: -- Summary: Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3 (was: Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.9.1) > Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3 > --- > > Key: HIVE-28043 > URL: https://issues.apache.org/jira/browse/HIVE-28043 > Project: Hive > Issue Type: Task >Reporter: Anmol Sundaram >Priority: Major > Labels: pull-request-available > > The recent stable version of ZK is 3.9.1 > We should see if we can have a similar upgrade for Hive as well > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-28041) Upgrade jetty to 9.4.53 due to CVE-2023-44487
[ https://issues.apache.org/jira/browse/HIVE-28041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813019#comment-17813019 ] Anmol Sundaram commented on HIVE-28041: --- Hive currently uses Apache DirServer 1.5.7, which is not compatible with Jetty 9.4.53. The Apache DirServer version compatible with this Jetty upgrade is 2.0.0.AM25+. Unfortunately, the tests failing upon using Apache DirServer 2.0.0.AM25 is genuine and caused by what seems to be a change in behaviour. Lodged a Jira to DirServer here - [DIRSERVER-2386|https://issues.apache.org/jira/browse/DIRSERVER-2386] > Upgrade jetty to 9.4.53 due to CVE-2023-44487 > - > > Key: HIVE-28041 > URL: https://issues.apache.org/jira/browse/HIVE-28041 > Project: Hive > Issue Type: Task > Components: Hive >Reporter: Anmol Sundaram >Priority: Major > Labels: pull-request-available > > At the time of raising this, Hadoop also uses Jetty 9.4.53 > Ref - https://github.com/apache/hadoop/blob/trunk/hadoop-project/pom.xml#L40 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28043) Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.9.1
[ https://issues.apache.org/jira/browse/HIVE-28043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28043: -- Description: The recent stable version of ZK is 3.9.1 We should see if we can have a similar upgrade for Hive as well was: Hadoop upgraded their Zookeeper versions to 3.8.3. See [HADOOP-18613|https://issues.apache.org/jira/browse/HADOOP-18613] We should see if we can have a similar upgrade for Hive as well > Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.9.1 > --- > > Key: HIVE-28043 > URL: https://issues.apache.org/jira/browse/HIVE-28043 > Project: Hive > Issue Type: Task >Reporter: Anmol Sundaram >Priority: Major > > The recent stable version of ZK is 3.9.1 > We should see if we can have a similar upgrade for Hive as well > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28043) Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.9.1
[ https://issues.apache.org/jira/browse/HIVE-28043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28043: -- Summary: Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.9.1 (was: Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3) > Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.9.1 > --- > > Key: HIVE-28043 > URL: https://issues.apache.org/jira/browse/HIVE-28043 > Project: Hive > Issue Type: Task >Reporter: Anmol Sundaram >Priority: Major > > Hadoop upgraded their Zookeeper versions to 3.8.3. See > [HADOOP-18613|https://issues.apache.org/jira/browse/HADOOP-18613] > We should see if we can have a similar upgrade for Hive as well > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28043) Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3
[ https://issues.apache.org/jira/browse/HIVE-28043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28043: -- Description: Hadoop upgraded their Zookeeper versions to 3.8.3. See [HADOOP-18613|https://issues.apache.org/jira/browse/HADOOP-18613] We should see if we can have a similar upgrade for Hive as well was: Hadoop upgraded their Zookeeper versions to 3.8.3 We should see if we can have a similar upgrade for Hive as well > Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3 > --- > > Key: HIVE-28043 > URL: https://issues.apache.org/jira/browse/HIVE-28043 > Project: Hive > Issue Type: Task >Reporter: Anmol Sundaram >Priority: Major > > Hadoop upgraded their Zookeeper versions to 3.8.3. See > [HADOOP-18613|https://issues.apache.org/jira/browse/HADOOP-18613] > We should see if we can have a similar upgrade for Hive as well > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28043) Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3
[ https://issues.apache.org/jira/browse/HIVE-28043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28043: -- Description: Hadoop upgraded their Zookeeper versions to 3.8.3 We should see if we can have a similar upgrade for Hive as well > Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3 > --- > > Key: HIVE-28043 > URL: https://issues.apache.org/jira/browse/HIVE-28043 > Project: Hive > Issue Type: Task >Reporter: Anmol Sundaram >Priority: Major > > Hadoop upgraded their Zookeeper versions to 3.8.3 > We should see if we can have a similar upgrade for Hive as well > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-28043) Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3
Anmol Sundaram created HIVE-28043: - Summary: Bump org.apache.zookeeper:zookeeper from 3.7.2 to 3.8.3 Key: HIVE-28043 URL: https://issues.apache.org/jira/browse/HIVE-28043 Project: Hive Issue Type: Task Reporter: Anmol Sundaram -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28041) Upgrade jetty to 9.4.53 due to CVE-2023-44487
[ https://issues.apache.org/jira/browse/HIVE-28041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28041: -- Description: At the time of raising this, Hadoop also uses Jetty 9.4.53 Ref - https://github.com/apache/hadoop/blob/trunk/hadoop-project/pom.xml#L40 > Upgrade jetty to 9.4.53 due to CVE-2023-44487 > - > > Key: HIVE-28041 > URL: https://issues.apache.org/jira/browse/HIVE-28041 > Project: Hive > Issue Type: Task > Components: Hive >Reporter: Anmol Sundaram >Priority: Major > Labels: pull-request-available > > At the time of raising this, Hadoop also uses Jetty 9.4.53 > Ref - https://github.com/apache/hadoop/blob/trunk/hadoop-project/pom.xml#L40 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28040) Upgrade netty to 4.1.100 due to CVE-2023-44487
[ https://issues.apache.org/jira/browse/HIVE-28040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28040: -- Description: At the time of raising this, Hadoop and Tez also use 4.1.100.Final in their trunk Related - https://issues.apache.org/jira/browse/TEZ-4538 > Upgrade netty to 4.1.100 due to CVE-2023-44487 > -- > > Key: HIVE-28040 > URL: https://issues.apache.org/jira/browse/HIVE-28040 > Project: Hive > Issue Type: Task > Components: Hive >Reporter: Anmol Sundaram >Priority: Major > Labels: pull-request-available > > At the time of raising this, Hadoop and Tez also use 4.1.100.Final in their > trunk > Related - https://issues.apache.org/jira/browse/TEZ-4538 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-28041) Upgrade jetty to 9.4.53 due to CVE-2023-44487
Anmol Sundaram created HIVE-28041: - Summary: Upgrade jetty to 9.4.53 due to CVE-2023-44487 Key: HIVE-28041 URL: https://issues.apache.org/jira/browse/HIVE-28041 Project: Hive Issue Type: Task Components: Hive Reporter: Anmol Sundaram -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-28040) Upgrade netty to 4.1.100 due to CVE-2023-44487
Anmol Sundaram created HIVE-28040: - Summary: Upgrade netty to 4.1.100 due to CVE-2023-44487 Key: HIVE-28040 URL: https://issues.apache.org/jira/browse/HIVE-28040 Project: Hive Issue Type: Task Components: Hive Reporter: Anmol Sundaram -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28000) Hive QL : "not in" clause gives incorrect results when type coercion cannot take place.
[ https://issues.apache.org/jira/browse/HIVE-28000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28000: -- Labels: (was: pull-request-available) > Hive QL : "not in" clause gives incorrect results when type coercion cannot > take place. > > > Key: HIVE-28000 > URL: https://issues.apache.org/jira/browse/HIVE-28000 > Project: Hive > Issue Type: Bug > Components: Hive >Reporter: Anmol Sundaram >Priority: Major > Attachments: not_in_examples.q > > > There are certain scenarios where "not in" clause gives incorrect results > when type coercion cannot take place. > These occur when the in clause contains at least one operand which cannot be > type-coerced to the column on which the in clause is being applied to. > > Please refer to the attached query examples for more details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
[ https://issues.apache.org/jira/browse/HIVE-27993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806719#comment-17806719 ] Anmol Sundaram commented on HIVE-27993: --- Hello [~abstractdog] , could you please help with the review as this is similar to TEZ-4394. > Netty4 ShuffleHandler: should use 1 boss thread > --- > > Key: HIVE-27993 > URL: https://issues.apache.org/jira/browse/HIVE-27993 > Project: Hive > Issue Type: Bug > Components: llap >Reporter: Anmol Sundaram >Priority: Major > Labels: pull-request-available > Attachments: HIVE-27993.01.patch > > > Similar to Tez TEZ-4394, and > [Hadoop|https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353], > [Hive LLAP > ShuffleHandler|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299] > should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28000) Hive QL : "not in" clause gives incorrect results when type coercion cannot take place.
[ https://issues.apache.org/jira/browse/HIVE-28000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28000: -- Attachment: not_in_examples.q > Hive QL : "not in" clause gives incorrect results when type coercion cannot > take place. > > > Key: HIVE-28000 > URL: https://issues.apache.org/jira/browse/HIVE-28000 > Project: Hive > Issue Type: Bug > Components: Hive >Reporter: Anmol Sundaram >Priority: Major > Attachments: not_in_examples.q > > > There are certain scenarios where "not in" clause gives incorrect results > when type coercion cannot take place. > These occur when the in clause contains at least one operand which cannot be > type-coerced to the column on which the in clause is being applied to. > > Please refer to the attached query examples for more details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28000) Hive QL : "not in" clause gives incorrect results when type coercion cannot take place.
[ https://issues.apache.org/jira/browse/HIVE-28000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-28000: -- Description: There are certain scenarios where "not in" clause gives incorrect results when type coercion cannot take place. These occur when the in clause contains at least one operand which cannot be type-coerced to the column on which the in clause is being applied to. Please refer to the attached query examples for more details. was: There are certain scenarios where "not in" clause gives incorrect results when type coercion cannot take place. These occur when the in clause contains all the operands, none of which can be type-coerced to the column on which the in clause is being applied to. Please refer to the attached query examples for more details. > Hive QL : "not in" clause gives incorrect results when type coercion cannot > take place. > > > Key: HIVE-28000 > URL: https://issues.apache.org/jira/browse/HIVE-28000 > Project: Hive > Issue Type: Bug > Components: Hive >Reporter: Anmol Sundaram >Priority: Major > > There are certain scenarios where "not in" clause gives incorrect results > when type coercion cannot take place. > These occur when the in clause contains at least one operand which cannot be > type-coerced to the column on which the in clause is being applied to. > > Please refer to the attached query examples for more details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-28000) Hive QL : "not in" clause gives incorrect results when type coercion cannot take place.
Anmol Sundaram created HIVE-28000: - Summary: Hive QL : "not in" clause gives incorrect results when type coercion cannot take place. Key: HIVE-28000 URL: https://issues.apache.org/jira/browse/HIVE-28000 Project: Hive Issue Type: Bug Components: Hive Reporter: Anmol Sundaram There are certain scenarios where "not in" clause gives incorrect results when type coercion cannot take place. These occur when the in clause contains all the operands, none of which can be type-coerced to the column on which the in clause is being applied to. Please refer to the attached query examples for more details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
[ https://issues.apache.org/jira/browse/HIVE-27993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805357#comment-17805357 ] Anmol Sundaram commented on HIVE-27993: --- Hello [~zabetak] , thanks for letting me know. I have created a PR. > Netty4 ShuffleHandler: should use 1 boss thread > --- > > Key: HIVE-27993 > URL: https://issues.apache.org/jira/browse/HIVE-27993 > Project: Hive > Issue Type: Bug > Components: llap >Reporter: Anmol Sundaram >Priority: Major > Labels: pull-request-available > Attachments: HIVE-27993.01.patch > > > Similar to Tez TEZ-4394, and > [Hadoop|https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353], > [Hive LLAP > ShuffleHandler|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299] > should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
[ https://issues.apache.org/jira/browse/HIVE-27993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-27993: -- Attachment: HIVE-27993.01.patch > Netty4 ShuffleHandler: should use 1 boss thread > --- > > Key: HIVE-27993 > URL: https://issues.apache.org/jira/browse/HIVE-27993 > Project: Hive > Issue Type: Bug > Components: llap >Reporter: Anmol Sundaram >Priority: Major > Attachments: HIVE-27993.01.patch > > > Similar to Tez TEZ-4394, and > [Hadoop|https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353], > [Hive LLAP > ShuffleHandler|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299] > should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
[ https://issues.apache.org/jira/browse/HIVE-27993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-27993: -- Description: Similar to Tez TEZ-4394, and [Hadoop|https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353], [Hive LLAP ShuffleHandler|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299] should also use a single thread for boss thread pool. (was: Similar to Tez TEZ-4394, and [Hadoop|#L353], [Hive LLAP ShuffleHandler|#L299] should also use a single thread for boss thread pool. ) > Netty4 ShuffleHandler: should use 1 boss thread > --- > > Key: HIVE-27993 > URL: https://issues.apache.org/jira/browse/HIVE-27993 > Project: Hive > Issue Type: Bug > Components: llap >Reporter: Anmol Sundaram >Priority: Major > > Similar to Tez TEZ-4394, and > [Hadoop|https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353], > [Hive LLAP > ShuffleHandler|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299] > should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
[ https://issues.apache.org/jira/browse/HIVE-27993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-27993: -- Description: Similar to Tez TEZ-4394, and [Hadoop|#L353]], [Hive LLAP ShuffleHandler|#L299]] should also use a single thread for boss thread pool. (was: Similar to Tez [TEZ-4394|https://issues.apache.org/jira/browse/TEZ-4394], and [Hadoop|[https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353]], [Hive LLAP ShuffleHandler|[https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299]|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299]should] should also use a single thread for boss thread pool. ) > Netty4 ShuffleHandler: should use 1 boss thread > --- > > Key: HIVE-27993 > URL: https://issues.apache.org/jira/browse/HIVE-27993 > Project: Hive > Issue Type: Bug > Components: llap >Reporter: Anmol Sundaram >Priority: Major > > Similar to Tez TEZ-4394, and [Hadoop|#L353]], [Hive LLAP > ShuffleHandler|#L299]] should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
[ https://issues.apache.org/jira/browse/HIVE-27993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anmol Sundaram updated HIVE-27993: -- Description: Similar to Tez TEZ-4394, and [Hadoop|#L353], [Hive LLAP ShuffleHandler|#L299] should also use a single thread for boss thread pool. (was: Similar to Tez TEZ-4394, and [Hadoop|#L353]], [Hive LLAP ShuffleHandler|#L299]] should also use a single thread for boss thread pool. ) > Netty4 ShuffleHandler: should use 1 boss thread > --- > > Key: HIVE-27993 > URL: https://issues.apache.org/jira/browse/HIVE-27993 > Project: Hive > Issue Type: Bug > Components: llap >Reporter: Anmol Sundaram >Priority: Major > > Similar to Tez TEZ-4394, and [Hadoop|#L353], [Hive LLAP ShuffleHandler|#L299] > should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27993) Netty4 ShuffleHandler: should use 1 boss thread
Anmol Sundaram created HIVE-27993: - Summary: Netty4 ShuffleHandler: should use 1 boss thread Key: HIVE-27993 URL: https://issues.apache.org/jira/browse/HIVE-27993 Project: Hive Issue Type: Bug Components: llap Reporter: Anmol Sundaram Similar to Tez [TEZ-4394|https://issues.apache.org/jira/browse/TEZ-4394], and [Hadoop|[https://github.com/apache/hadoop/blob/7a0903b7436e7f3fb4f07c40bed2218a2653ba38/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L353]], [Hive LLAP ShuffleHandler|[https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299]|https://github.com/apache/hive/blob/cc3f4d1d3b766f444606a4b06341eb8c4ae8148c/llap-server/src/java/org/apache/hadoop/hive/llap/shufflehandler/ShuffleHandler.java#L299]should] should also use a single thread for boss thread pool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683315#comment-17683315
]
Anmol Sundaram commented on HIVE-27004:
---
Thanks a lot for the suggestion [~hemanth619] . I have linked the GitHub PR.
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
>
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
> Labels: pull-request-available
> Attachments: HIVE-27004.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
> Sample repro code - jdoodle.com/ia/D5e
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-27004:
--
Attachment: HIVE-27004.patch
Status: Patch Available (was: Open)
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
>
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
> Attachments: HIVE-27004.patch
>
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
> Sample repro code - jdoodle.com/ia/D5e
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-27004:
--
Attachment: (was: HIVE-27004.patch)
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
>
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
> Attachments: HIVE-27004.patch
>
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
> Sample repro code - jdoodle.com/ia/D5e
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683008#comment-17683008
]
Anmol Sundaram commented on HIVE-27004:
---
Thanks a lot [~zabetak] and [~hemanth619] . Would really appreciate your help
in reviewing the patch.
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
>
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
> Attachments: HIVE-27004.patch
>
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
> Sample repro code - jdoodle.com/ia/D5e
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-27004:
--
Description:
Some of the unit tests related to _DateTimeFormatter_ were failing in Java
versions greater than 8 while working in Java 8.
Example of a failing Unit Test :
_org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
{code:java}
java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
could not be parsed, unparsed text found at index 23 at
java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
at
java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
at
org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
at
org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
at
org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method){code}
The {{appendZoneText(TextStyle)}} method of
[DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
when running [the
test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
in Java 11 , while it is working fine with Java 8.
According to the
[doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
, {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
as per the same
[doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
for higher Java
versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
{{appendZoneText().}}
This ensures the tests are passing for Java 8+ and based on my testing, I
didn’t see any regression of the change.
Sample repro code - jdoodle.com/ia/D5e
was:
Some of the unit tests related to _DateTimeFormatter_ were failing in Java
versions greater than 8 while working in Java 8.
Example of a failing Unit Test :
_org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
{code:java}
java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
could not be parsed, unparsed text found at index 23 at
java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
at
java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
at
org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
at
org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
at
org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method){code}
The {{appendZoneText(TextStyle)}} method of
[DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
when running [the
test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
in Java 11 , while it is working fine with Java 8.
According to the
[doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
, {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
as per the same
[doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
for higher Java
versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
{{appendZoneText().}}
This ensures the tests are passing for Java 8+ and based on my testing, I
didn’t see any regression of the change.
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions
[jira] [Updated] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-27004:
--
Attachment: HIVE-27004.patch
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
>
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
> Attachments: HIVE-27004.patch
>
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-27004:
--
Environment:
Java version used
{code:java}
openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
was:
Java version used
{{}}
{code:java}
openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
{{}}
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
>
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (HIVE-27004) DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
[
https://issues.apache.org/jira/browse/HIVE-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram reassigned HIVE-27004:
-
> DateTimeFormatterBuilder cannot parse 'UTC+' in Java versions higher than 8
> ---
>
> Key: HIVE-27004
> URL: https://issues.apache.org/jira/browse/HIVE-27004
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Environment: Java version used
> {{}}
> {code:java}
> openjdk version "11.0.16.1" 2022-08-12 LTS OpenJDK Runtime Environment
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS) OpenJDK 64-Bit Server VM
> Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed mode{code}
> {{}}
>Reporter: Anmol Sundaram
>Assignee: Anmol Sundaram
>Priority: Minor
>
> Some of the unit tests related to _DateTimeFormatter_ were failing in Java
> versions greater than 8 while working in Java 8.
> Example of a failing Unit Test :
> _org.apache.hadoop.hive.common.type.TestTimestampTZ#testComparision_
>
> {code:java}
> java.time.format.DateTimeParseException: Text '2017-04-14 18:00:00 UTC+08:00'
> could not be parsed, unparsed text found at index 23 at
> java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2049)
> at
> java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1874)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:76)
> at
> org.apache.hadoop.hive.common.type.TimestampTZUtil.parse(TimestampTZUtil.java:64)
> at
> org.apache.hadoop.hive.common.type.TestTimestampTZ.testComparison(TestTimestampTZ.java:44)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method){code}
>
> The {{appendZoneText(TextStyle)}} method of
> [DateTimeFormatteBuilder|https://github.com/apache/hive/blob/master/common/src/java/org/apache/hadoop/hive/common/type/TimestampTZUtil.java#L82]
> is not able to parse the {{+}} symbol in {{2017-04-14 18:00:00 UTC+08:00}}
> when running [the
> test|https://github.com/apache/hive/blob/master/common/src/test/org/apache/hadoop/hive/common/type/TestTimestampTZ.java#L37]
> in Java 11 , while it is working fine with Java 8.
> According to the
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendZoneText(java.time.format.TextStyle)]
> , {{appendZoneText(TextStyle)}} should be able to parse {{either the textual
> zone name, the zone ID or the offset}} and UTC+08:00 should come under offset
> as per the same
> [doc|https://developer.android.com/reference/java/time/format/DateTimeFormatterBuilder#appendOffset(java.lang.String,%20java.lang.String)].
> It seems, however, that "UTC" was explicitly removed [when parsed as ZoneText
> for higher Java
> versions|https://github.com/openjdk/jdk/commit/5c3a01591c5c945926636fdc9f164d60b5b4f29e?diff=unified#diff-5fcf976db1c06e8f44a8671356d7e34fdfbf5b057baa852e7c3e015c8797c889R4263]
> As a workaround, we can use {{appendZoneOrOffsetId()}} rather than
> {{appendZoneText().}}
> This ensures the tests are passing for Java 8+ and based on my testing, I
> didn’t see any regression of the change.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HIVE-24083) hcatalog error in Hadoop 3.3.0: authentication type needed
[
https://issues.apache.org/jira/browse/HIVE-24083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564223#comment-17564223
]
Anmol Sundaram edited comment on HIVE-24083 at 7/8/22 10:35 AM:
I was able to get it run by the following (temporary?) fix :
{code:java}
diff --git
a/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
b/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
index d183b2e61b..5e5c4132f4 100644
—
a/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
+++
b/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
@@ -38,6 +38,8 @@
import org.apache.hadoop.hive.shims.Utils;
import org.apache.hadoop.security.UserGroupInformation;
import org.apache.hadoop.security.authentication.client.PseudoAuthenticator;
+import org.apache.hadoop.security.authentication.server.AuthenticationFilter;
+import
org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler;
import
org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler;
import org.apache.hadoop.security.SecurityUtil;
import org.apache.hadoop.util.GenericOptionsParser;
@@ -269,6 +271,11 @@ public FilterHolder makeAuthFilter() throws IOException {
authFilter.setInitParameter("dfs.web.authentication.kerberos.keytab",
conf.kerberosKeytab());
}
+
+ authFilter.setInitParameter(AuthenticationFilter.AUTH_TYPE,
UserGroupInformation.isSecurityEnabled() ?
+ KerberosAuthenticationHandler.TYPE :
+ PseudoAuthenticationHandler.TYPE);
+
return authFilter;
}{code}
was (Author: JIRAUSER288438):
I was able to get it run by the following (temporary?) fix :
diff --git
a/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
b/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
index d183b2e61b..5e5c4132f4 100644
---
a/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
+++
b/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
@@ -38,6 +38,8 @@
import org.apache.hadoop.hive.shims.Utils;
import org.apache.hadoop.security.UserGroupInformation;
import org.apache.hadoop.security.authentication.client.PseudoAuthenticator;
+import org.apache.hadoop.security.authentication.server.AuthenticationFilter;
+import
org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler;
import
org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler;
import org.apache.hadoop.security.SecurityUtil;
import org.apache.hadoop.util.GenericOptionsParser;
@@ -269,6 +271,11 @@ public FilterHolder makeAuthFilter() throws IOException \{
authFilter.setInitParameter("dfs.web.authentication.kerberos.keytab",
conf.kerberosKeytab());
}
+
+authFilter.setInitParameter(AuthenticationFilter.AUTH_TYPE,
UserGroupInformation.isSecurityEnabled() ?
+KerberosAuthenticationHandler.TYPE :
+PseudoAuthenticationHandler.TYPE);
+
return authFilter;
}
> hcatalog error in Hadoop 3.3.0: authentication type needed
> --
>
> Key: HIVE-24083
> URL: https://issues.apache.org/jira/browse/HIVE-24083
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 3.1.2
>Reporter: Javier J. Salmeron Garcia
>Priority: Minor
>
> Using Hive 3.1.2, webhcat fails to start in Hadoop 3.3.0 with the following
> error:
> ```
> javax.servlet.ServletException: Authentication type must be specified:
> simple|kerberos
> ```
> I tried in Hadoop 3.2.1 with the exact settings and it starts without issues:
>
> ```
> webhcat: /tmp/hadoop-3.2.1//bin/hadoop jar
> /opt/bitnami/hadoop/hive/hcatalog/sbin/../share/webhcat/svr/lib/hive-webhcat-3.1.2.jar
> org.apache.hive.hcatalog.templeton.Main
> webhcat: starting ... started.
> webhcat: done
> ```
>
> I can provide more logs if needed. Detected authentication settings:
>
> ```
> hadoop.http.authentication.simple.anonymous.allowed=true
> hadoop.http.authentication.type=simple
> hadoop.security.authentication=simple
> ipc.client.fallback-to-simple-auth-allowed=false
> yarn.timeline-service.http-authentication.simple.anonymous.allowed=true
> yarn.timeline-service.http-authentication.type=simple
> ```
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-24083) hcatalog error in Hadoop 3.3.0: authentication type needed
[
https://issues.apache.org/jira/browse/HIVE-24083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564223#comment-17564223
]
Anmol Sundaram commented on HIVE-24083:
---
I was able to get it run by the following (temporary?) fix :
diff --git
a/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
b/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
index d183b2e61b..5e5c4132f4 100644
---
a/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
+++
b/hcatalog/webhcat/svr/src/main/java/org/apache/hive/hcatalog/templeton/Main.java
@@ -38,6 +38,8 @@
import org.apache.hadoop.hive.shims.Utils;
import org.apache.hadoop.security.UserGroupInformation;
import org.apache.hadoop.security.authentication.client.PseudoAuthenticator;
+import org.apache.hadoop.security.authentication.server.AuthenticationFilter;
+import
org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler;
import
org.apache.hadoop.security.authentication.server.PseudoAuthenticationHandler;
import org.apache.hadoop.security.SecurityUtil;
import org.apache.hadoop.util.GenericOptionsParser;
@@ -269,6 +271,11 @@ public FilterHolder makeAuthFilter() throws IOException \{
authFilter.setInitParameter("dfs.web.authentication.kerberos.keytab",
conf.kerberosKeytab());
}
+
+authFilter.setInitParameter(AuthenticationFilter.AUTH_TYPE,
UserGroupInformation.isSecurityEnabled() ?
+KerberosAuthenticationHandler.TYPE :
+PseudoAuthenticationHandler.TYPE);
+
return authFilter;
}
> hcatalog error in Hadoop 3.3.0: authentication type needed
> --
>
> Key: HIVE-24083
> URL: https://issues.apache.org/jira/browse/HIVE-24083
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 3.1.2
>Reporter: Javier J. Salmeron Garcia
>Priority: Minor
>
> Using Hive 3.1.2, webhcat fails to start in Hadoop 3.3.0 with the following
> error:
> ```
> javax.servlet.ServletException: Authentication type must be specified:
> simple|kerberos
> ```
> I tried in Hadoop 3.2.1 with the exact settings and it starts without issues:
>
> ```
> webhcat: /tmp/hadoop-3.2.1//bin/hadoop jar
> /opt/bitnami/hadoop/hive/hcatalog/sbin/../share/webhcat/svr/lib/hive-webhcat-3.1.2.jar
> org.apache.hive.hcatalog.templeton.Main
> webhcat: starting ... started.
> webhcat: done
> ```
>
> I can provide more logs if needed. Detected authentication settings:
>
> ```
> hadoop.http.authentication.simple.anonymous.allowed=true
> hadoop.http.authentication.type=simple
> hadoop.security.authentication=simple
> ipc.client.fallback-to-simple-auth-allowed=false
> yarn.timeline-service.http-authentication.simple.anonymous.allowed=true
> yarn.timeline-service.http-authentication.type=simple
> ```
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-26286) Hive WebHCat Tests are failing
[
https://issues.apache.org/jira/browse/HIVE-26286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562017#comment-17562017
]
Anmol Sundaram commented on HIVE-26286:
---
Hi all, can someone please take a look on that ?
> Hive WebHCat Tests are failing
> --
>
> Key: HIVE-26286
> URL: https://issues.apache.org/jira/browse/HIVE-26286
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 4.0.0
> Environment: [link title|http://example.com]
>Reporter: Anmol Sundaram
>Priority: Major
>
> The Hive TestWebHCatE2e tests seem to be failing due to
>
> {quote}templeton: Server failed to start: null
> [main] ERROR org.apache.hive.hcatalog.templeton.Main - Server failed to
> start:
> java.lang.NullPointerException
> at
> org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:174)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
> at org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:220)
> at org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:143)
> at
> org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
> at org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252)
> at org.apache.hive.hcatalog.templeton.Main.run(Main.java:147)
> at
> org.apache.hive.hcatalog.templeton.TestWebHCatE2e.startHebHcatInMem(TestWebHCatE2e.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59){quote}
> {quote} {quote}
> This seems to be caused due to HIVE-18728 , which is breaking.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-24484) Upgrade Hadoop to 3.3.3
[ https://issues.apache.org/jira/browse/HIVE-24484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552589#comment-17552589 ] Anmol Sundaram commented on HIVE-24484: --- Hi [~ayushtkn] , can we please ensure that these two JIIRAs are not blockers for upgrading to Hadoop 3.3 https://issues.apache.org/jira/browse/HIVE-24083 https://issues.apache.org/jira/browse/HIVE-26286 They seem to be causing WebHCatalog related issues > Upgrade Hadoop to 3.3.3 > --- > > Key: HIVE-24484 > URL: https://issues.apache.org/jira/browse/HIVE-24484 > Project: Hive > Issue Type: Improvement >Reporter: David Mollitor >Assignee: Ayush Saxena >Priority: Major > Labels: pull-request-available > Time Spent: 12h 13m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HIVE-26286) Hive WebHCat Tests are failing
[
https://issues.apache.org/jira/browse/HIVE-26286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-26286:
--
Description:
The Hive TestWebHCatE2e tests seem to be failing due to
{quote}templeton: Server failed to start: null
[main] ERROR org.apache.hive.hcatalog.templeton.Main - Server failed to start:
java.lang.NullPointerException
at org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:174)
at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
at org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:220)
at org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:143)
at org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
at org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252)
at org.apache.hive.hcatalog.templeton.Main.run(Main.java:147)
at
org.apache.hive.hcatalog.templeton.TestWebHCatE2e.startHebHcatInMem(TestWebHCatE2e.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59){quote}
{quote} {quote}
This seems to be caused due to HIVE-18728 , which is breaking.
was:
The Hive TestWebHCatE2e tests seem to be failing due to
{quote}
templeton: Server failed to start: null2022-05-31T21:51:13,711 ERROR [main]
templeton.Main: Server failed to start: java.lang.NullPointerException: null at
org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:186)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:215)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:145)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
~[classes/:?] at
org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252) ~[classes/:?]
{quote}
This seems to be caused due to HIVE-18728 , which is breaking.
> Hive WebHCat Tests are failing
> --
>
> Key: HIVE-26286
> URL: https://issues.apache.org/jira/browse/HIVE-26286
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 4.0.0
> Environment: [link title|http://example.com]
>Reporter: Anmol Sundaram
>Priority: Major
>
> The Hive TestWebHCatE2e tests seem to be failing due to
>
> {quote}templeton: Server failed to start: null
> [main] ERROR org.apache.hive.hcatalog.templeton.Main - Server failed to
> start:
> java.lang.NullPointerException
> at
> org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:174)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
> at org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:220)
> at org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:143)
> at
> org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
> at org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252)
> at org.apache.hive.hcatalog.templeton.Main.run(Main.java:147)
> at
> org.apache.hive.hcatalog.templeton.TestWebHCatE2e.startHebHcatInMem(TestWebHCatE2e.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59){quote}
> {quote} {quote}
> This seems to be caused due to HIVE-18728 , which is breaking.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (HIVE-26286) Hive WebHCat Tests are failing
[
https://issues.apache.org/jira/browse/HIVE-26286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anmol Sundaram updated HIVE-26286:
--
Description:
The Hive TestWebHCatE2e tests seem to be failing due to
{quote}
templeton: Server failed to start: null2022-05-31T21:51:13,711 ERROR [main]
templeton.Main: Server failed to start: java.lang.NullPointerException: null at
org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:186)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:215)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:145)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
~[classes/:?] at
org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252) ~[classes/:?]
{quote}
This seems to be caused due to HIVE-18728 , which is breaking.
was:
The Hive TestWebHCatE2e tests seem to be failing due to
templeton: Server failed to start: null2022-05-31T21:51:13,711 ERROR [main]
templeton.Main: Server failed to start: java.lang.NullPointerException: null
at
org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:186)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:215)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:145)
~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
~[classes/:?] at
org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252) ~[classes/:?]
This seems to be caused due to
[HIVE-18728|https://issues.apache.org/jira/browse/HIVE-18728] , which is
breaking.
> Hive WebHCat Tests are failing
> --
>
> Key: HIVE-26286
> URL: https://issues.apache.org/jira/browse/HIVE-26286
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 4.0.0
> Environment: [link title|http://example.com]
>Reporter: Anmol Sundaram
>Priority: Major
>
> The Hive TestWebHCatE2e tests seem to be failing due to
>
> {quote}
> templeton: Server failed to start: null2022-05-31T21:51:13,711 ERROR [main]
> templeton.Main: Server failed to start: java.lang.NullPointerException: null
> at
> org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:186)
> ~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
> org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
> ~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
> org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:215)
> ~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
> org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:145)
> ~[jetty-server-9.4.43.v20210629.jar:9.4.43.v20210629] at
> org.apache.hive.hcatalog.templeton.Main.createChannelConnector(Main.java:295)
> ~[classes/:?] at
> org.apache.hive.hcatalog.templeton.Main.runServer(Main.java:252) ~[classes/:?]
>
> {quote}
> This seems to be caused due to HIVE-18728 , which is breaking.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (HIVE-26214) Hive 3.1.3 Release Notes
[ https://issues.apache.org/jira/browse/HIVE-26214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536615#comment-17536615 ] Anmol Sundaram edited comment on HIVE-26214 at 5/13/22 12:35 PM: - Hello [~zabetak] , yes thats correct. The Release Notes include some of the JIIRAs that are unresolved ( HIVE-25567 ) while some of the commits are missing, which leads to confusion on relying on the release notes was (Author: JIRAUSER288438): Hello [~zabetak] , yes thats correct. The Release Notes include some of the JIIRAs that are unresolved ( HIVE-25567 ) while some of the commits are missing, which leads to confusion > Hive 3.1.3 Release Notes > > > Key: HIVE-26214 > URL: https://issues.apache.org/jira/browse/HIVE-26214 > Project: Hive > Issue Type: Improvement > Components: Documentation, Hive >Affects Versions: 3.1.3 >Reporter: Anmol Sundaram >Priority: Minor > > The Hive Release Notes as mentioned in > [here|https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346277=Html=12310843] > does not seem to be accurate when compared with the [commit > logs|https://github.com/apache/hive/commits/rel/release-3.1.3]. > Can we please get this updated, if applicable ? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (HIVE-26214) Hive 3.1.3 Release Notes
[ https://issues.apache.org/jira/browse/HIVE-26214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536615#comment-17536615 ] Anmol Sundaram commented on HIVE-26214: --- Hello [~zabetak] , yes thats correct. The Release Notes include some of the JIIRAs that are unresolved ( HIVE-25567 ) while some of the commits are missing, which leads to confusion > Hive 3.1.3 Release Notes > > > Key: HIVE-26214 > URL: https://issues.apache.org/jira/browse/HIVE-26214 > Project: Hive > Issue Type: Improvement > Components: Documentation, Hive >Affects Versions: 3.1.3 >Reporter: Anmol Sundaram >Priority: Minor > > The Hive Release Notes as mentioned in > [here|https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346277=Html=12310843] > does not seem to be accurate when compared with the [commit > logs|https://github.com/apache/hive/commits/rel/release-3.1.3]. > Can we please get this updated, if applicable ? -- This message was sent by Atlassian Jira (v8.20.7#820007)
