[jira] [Commented] (HIVE-27910) Hive on Spark -- should work?
[
https://issues.apache.org/jira/browse/HIVE-27910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789770#comment-17789770
]
zhangbutao commented on HIVE-27910:
---
[https://cwiki.apache.org/confluence/display/Hive/Hive+on+Spark] yep, I think
we need add notes to remind users that Hive on Spark was not supported since
Hive4.
> Hive on Spark -- should work?
> -
>
> Key: HIVE-27910
> URL: https://issues.apache.org/jira/browse/HIVE-27910
> Project: Hive
> Issue Type: Task
>Affects Versions: 3.1.1
>Reporter: Alexander Petrossian (PAF)
>Priority: Major
>
> I wanted to test this
> [https://cwiki.apache.org/confluence/display/Hive/Hive+on+Spark]
> Where our admins installed
> {code:java}
> hive --version
> Hive 3.1.0.3.1.0.0-78
> Git
> git://ctr-e138-1518143905142-586755-01-15.hwx.site/grid/0/jenkins/workspace/HDP-parallel-centos7/SOURCES/hive
> -r 56673b027117d8cb3400675b1680a4d992360808 {code}
> Trying
> {code:java}
> set hive.execution.engine=spark;
> SELECT ...; {code}
> Getting
> {code:java}
> ERROR : FAILED: Execution Error, return code 30041 from
> org.apache.hadoop.hive.ql.exec.spark.SparkTask. Failed to create Spark client
> for Spark session 139c0453-459f-4511-b7fc-eab28e78fe0c {code}
> Could it be that Spark support in Hive was somehow dropped?
> Or could it be some [simple?] configuration issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-27910) Hive on Spark -- should work?
[
https://issues.apache.org/jira/browse/HIVE-27910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789769#comment-17789769
]
Alexander Petrossian (PAF) commented on HIVE-27910:
---
Thanks a lot!
Maybe this issue could be used to remember to remove
[https://cwiki.apache.org/confluence/display/Hive/Hive+on+Spark%3A+Getting+Started]
?
> Hive on Spark -- should work?
> -
>
> Key: HIVE-27910
> URL: https://issues.apache.org/jira/browse/HIVE-27910
> Project: Hive
> Issue Type: Task
>Affects Versions: 3.1.1
>Reporter: Alexander Petrossian (PAF)
>Priority: Major
>
> I wanted to test this
> [https://cwiki.apache.org/confluence/display/Hive/Hive+on+Spark]
> Where our admins installed
> {code:java}
> hive --version
> Hive 3.1.0.3.1.0.0-78
> Git
> git://ctr-e138-1518143905142-586755-01-15.hwx.site/grid/0/jenkins/workspace/HDP-parallel-centos7/SOURCES/hive
> -r 56673b027117d8cb3400675b1680a4d992360808 {code}
> Trying
> {code:java}
> set hive.execution.engine=spark;
> SELECT ...; {code}
> Getting
> {code:java}
> ERROR : FAILED: Execution Error, return code 30041 from
> org.apache.hadoop.hive.ql.exec.spark.SparkTask. Failed to create Spark client
> for Spark session 139c0453-459f-4511-b7fc-eab28e78fe0c {code}
> Could it be that Spark support in Hive was somehow dropped?
> Or could it be some [simple?] configuration issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-27910) Hive on Spark -- should work?
[
https://issues.apache.org/jira/browse/HIVE-27910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789765#comment-17789765
]
zhangbutao commented on HIVE-27910:
---
Hive on Spark is removed in Hive4 version. IMO, for Hive3.1.1, no one maintains
this feature anymore.
I would suggest you use Hive on tez which is actively maintained by Hive
community.
Thanks.
> Hive on Spark -- should work?
> -
>
> Key: HIVE-27910
> URL: https://issues.apache.org/jira/browse/HIVE-27910
> Project: Hive
> Issue Type: Task
>Affects Versions: 3.1.1
>Reporter: Alexander Petrossian (PAF)
>Priority: Major
>
> I wanted to test this
> [https://cwiki.apache.org/confluence/display/Hive/Hive+on+Spark]
> Where our admins installed
> {code:java}
> hive --version
> Hive 3.1.0.3.1.0.0-78
> Git
> git://ctr-e138-1518143905142-586755-01-15.hwx.site/grid/0/jenkins/workspace/HDP-parallel-centos7/SOURCES/hive
> -r 56673b027117d8cb3400675b1680a4d992360808 {code}
> Trying
> {code:java}
> set hive.execution.engine=spark;
> SELECT ...; {code}
> Getting
> {code:java}
> ERROR : FAILED: Execution Error, return code 30041 from
> org.apache.hadoop.hive.ql.exec.spark.SparkTask. Failed to create Spark client
> for Spark session 139c0453-459f-4511-b7fc-eab28e78fe0c {code}
> Could it be that Spark support in Hive was somehow dropped?
> Or could it be some [simple?] configuration issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HIVE-23783) Support compaction in qtests
[ https://issues.apache.org/jira/browse/HIVE-23783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] László Bodor resolved HIVE-23783. - Fix Version/s: Not Applicable Resolution: Duplicate > Support compaction in qtests > > > Key: HIVE-23783 > URL: https://issues.apache.org/jira/browse/HIVE-23783 > Project: Hive > Issue Type: Improvement >Reporter: László Bodor >Assignee: László Bodor >Priority: Major > Fix For: Not Applicable > > > From time to time I get back to a scenario where I want to investigate a > compaction related issue and I have a complete repro SQL script for that. In > this case, I would prefer a qtest in which I can run manually triggered > compaction instead of setting up other kinds of unit tests. > This can be quite challenging, but the most important is that a compactor > environment (compactor threads, queue, etc.) cannot be set on the fly in the > scripts. Fortunately, we already have some preprocessed meta stuff in qtest > which can run in advance, it worth try that for this purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-23783) Support compaction in qtests
[ https://issues.apache.org/jira/browse/HIVE-23783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789697#comment-17789697 ] László Bodor commented on HIVE-23783: - not sure when this was implemented, but it's already possible in qtests > Support compaction in qtests > > > Key: HIVE-23783 > URL: https://issues.apache.org/jira/browse/HIVE-23783 > Project: Hive > Issue Type: Improvement >Reporter: László Bodor >Assignee: László Bodor >Priority: Major > > From time to time I get back to a scenario where I want to investigate a > compaction related issue and I have a complete repro SQL script for that. In > this case, I would prefer a qtest in which I can run manually triggered > compaction instead of setting up other kinds of unit tests. > This can be quite challenging, but the most important is that a compactor > environment (compactor threads, queue, etc.) cannot be set on the fly in the > scripts. Fortunately, we already have some preprocessed meta stuff in qtest > which can run in advance, it worth try that for this purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27842) Backport HIVE-21866: LLAP status service driver may get stuck with wrong Yarn app ID
[ https://issues.apache.org/jira/browse/HIVE-27842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan resolved HIVE-27842. - Resolution: Fixed > Backport HIVE-21866: LLAP status service driver may get stuck with wrong Yarn > app ID > > > Key: HIVE-27842 > URL: https://issues.apache.org/jira/browse/HIVE-27842 > Project: Hive > Issue Type: Sub-task >Reporter: Sruthi Mooriyathvariam >Assignee: Sruthi Mooriyathvariam >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > > HIVE-21866: LLAP status service driver may get stuck with wrong Yarn app ID > (Adam Szita).This requires backport of HIVE-20807: Refactor > LlapStatusServiceDriver and HIVE-20752: In case of LLAP start failure add > info how to find YARN logs > h1. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27842) Backport HIVE-21866: LLAP status service driver may get stuck with wrong Yarn app ID
[ https://issues.apache.org/jira/browse/HIVE-27842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-27842: Affects Version/s: 3.1.3 > Backport HIVE-21866: LLAP status service driver may get stuck with wrong Yarn > app ID > > > Key: HIVE-27842 > URL: https://issues.apache.org/jira/browse/HIVE-27842 > Project: Hive > Issue Type: Sub-task >Affects Versions: 3.1.3 >Reporter: Sruthi Mooriyathvariam >Assignee: Sruthi Mooriyathvariam >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > > HIVE-21866: LLAP status service driver may get stuck with wrong Yarn app ID > (Adam Szita).This requires backport of HIVE-20807: Refactor > LlapStatusServiceDriver and HIVE-20752: In case of LLAP start failure add > info how to find YARN logs > h1. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27842) Backport HIVE-21866: LLAP status service driver may get stuck with wrong Yarn app ID
[ https://issues.apache.org/jira/browse/HIVE-27842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27842: -- Labels: pull-request-available (was: ) > Backport HIVE-21866: LLAP status service driver may get stuck with wrong Yarn > app ID > > > Key: HIVE-27842 > URL: https://issues.apache.org/jira/browse/HIVE-27842 > Project: Hive > Issue Type: Sub-task >Reporter: Sruthi Mooriyathvariam >Assignee: Sruthi Mooriyathvariam >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > > HIVE-21866: LLAP status service driver may get stuck with wrong Yarn app ID > (Adam Szita).This requires backport of HIVE-20807: Refactor > LlapStatusServiceDriver and HIVE-20752: In case of LLAP start failure add > info how to find YARN logs > h1. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
