[jira] [Updated] (HIVE-27662) Incorrect parsing of complex type during vectorized text processing of data having multiple delimiters
[ https://issues.apache.org/jira/browse/HIVE-27662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav Aggarwal updated HIVE-27662: --- Target Version/s: (was: 4.0.0-beta-1) > Incorrect parsing of complex type during vectorized text processing of data > having multiple delimiters > -- > > Key: HIVE-27662 > URL: https://issues.apache.org/jira/browse/HIVE-27662 > Project: Hive > Issue Type: Bug > Components: Vectorization >Reporter: Raghav Aggarwal >Assignee: Raghav Aggarwal >Priority: Major > > When reading the data from text file format (with vectorizaton on) which > contains multiple delimiter like ^A ^B ^C ^D etc i.e (\u0001, \u0002, \u0003, > \u0004), incorrect parsing of data is happening which leads to incorrect > result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HIVE-27662) Incorrect parsing of complex type during vectorized text processing of data having multiple delimiters
[ https://issues.apache.org/jira/browse/HIVE-27662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-27662 started by Raghav Aggarwal. -- > Incorrect parsing of complex type during vectorized text processing of data > having multiple delimiters > -- > > Key: HIVE-27662 > URL: https://issues.apache.org/jira/browse/HIVE-27662 > Project: Hive > Issue Type: Bug > Components: Vectorization >Reporter: Raghav Aggarwal >Assignee: Raghav Aggarwal >Priority: Major > > When reading the data from text file format (with vectorizaton on) which > contains multiple delimiter like ^A ^B ^C ^D etc i.e (\u0001, \u0002, \u0003, > \u0004), incorrect parsing of data is happening which leads to incorrect > result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27662) Incorrect parsing of complex type during vectorized text processing of data having multiple delimiters
Raghav Aggarwal created HIVE-27662: -- Summary: Incorrect parsing of complex type during vectorized text processing of data having multiple delimiters Key: HIVE-27662 URL: https://issues.apache.org/jira/browse/HIVE-27662 Project: Hive Issue Type: Bug Components: Vectorization Reporter: Raghav Aggarwal Assignee: Raghav Aggarwal When reading the data from text file format (with vectorizaton on) which contains multiple delimiter like ^A ^B ^C ^D etc i.e (\u0001, \u0002, \u0003, \u0004), incorrect parsing of data is happening which leads to incorrect result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27566) Fix some yarn cluster options for tests
[
https://issues.apache.org/jira/browse/HIVE-27566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor resolved HIVE-27566.
-
Resolution: Fixed
> Fix some yarn cluster options for tests
> ---
>
> Key: HIVE-27566
> URL: https://issues.apache.org/jira/browse/HIVE-27566
> Project: Hive
> Issue Type: Bug
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Currently, on apache master, running a minihs2 and trying to insert a record
> fails, because the memory defined for node managers are less then what a
> query asks for.
> How to reproduce
> {code}
> mvn test -Dtest=StartMiniHS2Cluster -DminiHS2.clusterType=Tez
> -DminiHS2.run=true -DminiHS2.usePortsFromConf=true
> -Dpackaging.minimizeJar=false -T 1C -DskipShade -Dremoteresources.skip=true
> -Dmaven.javadoc.skip=true -Denforcer.skip=true -pl itests/hive-unit -Pitests
> mvn clean install -DskipTests -Pitests
> beeline -u "jdbc:hive2://localhost:1/default" -n $USER
> CREATE TABLE test_part(id int)
> PARTITIONED BY(dt string)
> STORED AS ORC;
> insert into test_part values (1, '1');
> {code}
> leads to:
> {code}
> Error: Error while compiling statement: FAILED: Execution Error, return code
> 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask.
> org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid
> resource request! Cannot allocate containers as requested resource is greater
> than maximum allowed allocation. Requested resource type=[memory-mb],
> Requested resource=, maximum allowed
> allocation=, please note that maximum allowed
> allocation is calculated by scheduler based on maximum resource of registered
> NodeManagers, which might be less than configured maximum
> allocation=
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27566) Fix some yarn cluster options for tests
[
https://issues.apache.org/jira/browse/HIVE-27566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-27566:
Fix Version/s: 4.0.0
(was: 4.0.0-beta-1)
> Fix some yarn cluster options for tests
> ---
>
> Key: HIVE-27566
> URL: https://issues.apache.org/jira/browse/HIVE-27566
> Project: Hive
> Issue Type: Bug
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Currently, on apache master, running a minihs2 and trying to insert a record
> fails, because the memory defined for node managers are less then what a
> query asks for.
> How to reproduce
> {code}
> mvn test -Dtest=StartMiniHS2Cluster -DminiHS2.clusterType=Tez
> -DminiHS2.run=true -DminiHS2.usePortsFromConf=true
> -Dpackaging.minimizeJar=false -T 1C -DskipShade -Dremoteresources.skip=true
> -Dmaven.javadoc.skip=true -Denforcer.skip=true -pl itests/hive-unit -Pitests
> mvn clean install -DskipTests -Pitests
> beeline -u "jdbc:hive2://localhost:1/default" -n $USER
> CREATE TABLE test_part(id int)
> PARTITIONED BY(dt string)
> STORED AS ORC;
> insert into test_part values (1, '1');
> {code}
> leads to:
> {code}
> Error: Error while compiling statement: FAILED: Execution Error, return code
> 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask.
> org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid
> resource request! Cannot allocate containers as requested resource is greater
> than maximum allowed allocation. Requested resource type=[memory-mb],
> Requested resource=, maximum allowed
> allocation=, please note that maximum allowed
> allocation is calculated by scheduler based on maximum resource of registered
> NodeManagers, which might be less than configured maximum
> allocation=
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27566) Fix some yarn cluster options for tests
[
https://issues.apache.org/jira/browse/HIVE-27566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-27566:
Fix Version/s: 4.0.0-beta-1
> Fix some yarn cluster options for tests
> ---
>
> Key: HIVE-27566
> URL: https://issues.apache.org/jira/browse/HIVE-27566
> Project: Hive
> Issue Type: Bug
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-beta-1
>
>
> Currently, on apache master, running a minihs2 and trying to insert a record
> fails, because the memory defined for node managers are less then what a
> query asks for.
> How to reproduce
> {code}
> mvn test -Dtest=StartMiniHS2Cluster -DminiHS2.clusterType=Tez
> -DminiHS2.run=true -DminiHS2.usePortsFromConf=true
> -Dpackaging.minimizeJar=false -T 1C -DskipShade -Dremoteresources.skip=true
> -Dmaven.javadoc.skip=true -Denforcer.skip=true -pl itests/hive-unit -Pitests
> mvn clean install -DskipTests -Pitests
> beeline -u "jdbc:hive2://localhost:1/default" -n $USER
> CREATE TABLE test_part(id int)
> PARTITIONED BY(dt string)
> STORED AS ORC;
> insert into test_part values (1, '1');
> {code}
> leads to:
> {code}
> Error: Error while compiling statement: FAILED: Execution Error, return code
> 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask.
> org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid
> resource request! Cannot allocate containers as requested resource is greater
> than maximum allowed allocation. Requested resource type=[memory-mb],
> Requested resource=, maximum allowed
> allocation=, please note that maximum allowed
> allocation is calculated by scheduler based on maximum resource of registered
> NodeManagers, which might be less than configured maximum
> allocation=
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-27566) Fix some yarn cluster options for tests
[
https://issues.apache.org/jira/browse/HIVE-27566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760916#comment-17760916
]
László Bodor commented on HIVE-27566:
-
merged to master, thanks [~ayushtkn] and [~simhadri-g] for the review!
> Fix some yarn cluster options for tests
> ---
>
> Key: HIVE-27566
> URL: https://issues.apache.org/jira/browse/HIVE-27566
> Project: Hive
> Issue Type: Bug
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
>
> Currently, on apache master, running a minihs2 and trying to insert a record
> fails, because the memory defined for node managers are less then what a
> query asks for.
> How to reproduce
> {code}
> mvn test -Dtest=StartMiniHS2Cluster -DminiHS2.clusterType=Tez
> -DminiHS2.run=true -DminiHS2.usePortsFromConf=true
> -Dpackaging.minimizeJar=false -T 1C -DskipShade -Dremoteresources.skip=true
> -Dmaven.javadoc.skip=true -Denforcer.skip=true -pl itests/hive-unit -Pitests
> mvn clean install -DskipTests -Pitests
> beeline -u "jdbc:hive2://localhost:1/default" -n $USER
> CREATE TABLE test_part(id int)
> PARTITIONED BY(dt string)
> STORED AS ORC;
> insert into test_part values (1, '1');
> {code}
> leads to:
> {code}
> Error: Error while compiling statement: FAILED: Execution Error, return code
> 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask.
> org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid
> resource request! Cannot allocate containers as requested resource is greater
> than maximum allowed allocation. Requested resource type=[memory-mb],
> Requested resource=, maximum allowed
> allocation=, please note that maximum allowed
> allocation is calculated by scheduler based on maximum resource of registered
> NodeManagers, which might be less than configured maximum
> allocation=
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27661) Auth mode inferred from the Authorization header
[ https://issues.apache.org/jira/browse/HIVE-27661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergely Farkas updated HIVE-27661: -- Description: In HIVE-27352 we added support for multiple authentication modes and this change introduced the "auth" http header, which broke compatibility with Impala in the following case: The impala-shell client tool is able to connect to HS2 with the authentication mode specified first in the auth mode list, but the other auth options do not work because the impala-shell does not send an "auth" header to HS2. In a discussion with impala devs, it turned out that impala does not need a similar header to identify the authentication mode, because in case of http transport, the content of the Authorization header can be used to infer the auth mode. This improvement aims at avoiding the use of the "auth" header and thus allows us to connect to HS2 via http protocol even if multiple authentication modes are enabled and the client does not use the "auth" header (e.g. impala-shell or older jdbc driver builds). > Auth mode inferred from the Authorization header > > > Key: HIVE-27661 > URL: https://issues.apache.org/jira/browse/HIVE-27661 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Gergely Farkas >Assignee: Gergely Farkas >Priority: Major > > In HIVE-27352 we added support for multiple authentication modes and this > change introduced the "auth" http header, > which broke compatibility with Impala in the following case: The impala-shell > client tool is able to connect to HS2 with the authentication mode specified > first in the auth mode list, but the other auth options do not work because > the impala-shell does not send an "auth" header to HS2. In a discussion with > impala devs, it turned out that impala does not need a similar header to > identify the authentication mode, because in case of http transport, the > content of the Authorization header can be used to infer the auth mode. This > improvement aims at avoiding the use of the "auth" header and thus allows us > to connect to HS2 via http protocol even if multiple authentication modes are > enabled and the client does not use the "auth" header (e.g. impala-shell or > older jdbc driver builds). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HIVE-27661) Auth mode inferred from the Authorization header
[ https://issues.apache.org/jira/browse/HIVE-27661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-27661 started by Gergely Farkas. - > Auth mode inferred from the Authorization header > > > Key: HIVE-27661 > URL: https://issues.apache.org/jira/browse/HIVE-27661 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 >Reporter: Gergely Farkas >Assignee: Gergely Farkas >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27661) Auth mode inferred from the Authorization header
Gergely Farkas created HIVE-27661: - Summary: Auth mode inferred from the Authorization header Key: HIVE-27661 URL: https://issues.apache.org/jira/browse/HIVE-27661 Project: Hive Issue Type: Improvement Components: HiveServer2 Reporter: Gergely Farkas Assignee: Gergely Farkas -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27660) Update some test results for branch-2.3
[ https://issues.apache.org/jira/browse/HIVE-27660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27660: -- Labels: pull-request-available (was: ) > Update some test results for branch-2.3 > --- > > Key: HIVE-27660 > URL: https://issues.apache.org/jira/browse/HIVE-27660 > Project: Hive > Issue Type: Test > Components: Test >Affects Versions: 2.3.10 >Reporter: Yuming Wang >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27660) Update some test results for branch-2.3
Yuming Wang created HIVE-27660: -- Summary: Update some test results for branch-2.3 Key: HIVE-27660 URL: https://issues.apache.org/jira/browse/HIVE-27660 Project: Hive Issue Type: Test Components: Test Affects Versions: 2.3.10 Reporter: Yuming Wang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27659) Make partition order configurable if we are not returning all partitions
[ https://issues.apache.org/jira/browse/HIVE-27659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27659: -- Labels: pull-request-available (was: ) > Make partition order configurable if we are not returning all partitions > > > Key: HIVE-27659 > URL: https://issues.apache.org/jira/browse/HIVE-27659 > Project: Hive > Issue Type: Improvement > Components: Metastore >Affects Versions: 4.0.0-beta-1 >Reporter: Yuming Wang >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27659) Make partition order configurable if we are not returning all partitions
Yuming Wang created HIVE-27659: -- Summary: Make partition order configurable if we are not returning all partitions Key: HIVE-27659 URL: https://issues.apache.org/jira/browse/HIVE-27659 Project: Hive Issue Type: Improvement Components: Metastore Affects Versions: 4.0.0-beta-1 Reporter: Yuming Wang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27628) implement array_remove UDF in Hive
[
https://issues.apache.org/jira/browse/HIVE-27628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taraka Rama Rao Lethavadla resolved HIVE-27628.
---
Fix Version/s: 4.0.0-beta-1
Resolution: Fixed
> implement array_remove UDF in Hive
> --
>
> Key: HIVE-27628
> URL: https://issues.apache.org/jira/browse/HIVE-27628
> Project: Hive
> Issue Type: Sub-task
>Reporter: Taraka Rama Rao Lethavadla
>Assignee: Taraka Rama Rao Lethavadla
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-beta-1
>
>
> *array_remove(array, element)*
> Removes all occurrences of {{element}} from {{{}array{}}}.
>
> Example:
> {noformat}
> > SELECT array_remove(array(1, 2, 3,4,2), 2) FROM src;
> [1,3,4]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
