[
https://issues.apache.org/jira/browse/SPARK-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078556#comment-14078556
]
Cheng Lian commented on SPARK-2472:
-----------------------------------
This bug only affects queries involve insertion, like the CTAS statement in the
given example. The reason is that {{InsertIntoHiveTable.execute()}} submits a
job to perform the insertion eagerly at the end of the query planning phase. At
that time, the job description hasn't been updated, thus shows the previous one.
> Spark SQL Thrift server sometimes assigns wrong job group name
> --------------------------------------------------------------
>
> Key: SPARK-2472
> URL: https://issues.apache.org/jira/browse/SPARK-2472
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.0.0
> Reporter: Cheng Lian
> Priority: Minor
>
> Sample beeline session used to reproduce this issue:
> {code}
> 0: jdbc:hive2://localhost:10000> drop table test;
> +---------+
> | result |
> +---------+
> +---------+
> No rows selected (0.614 seconds)
> 0: jdbc:hive2://localhost:10000> create table hive_table_copy as select *
> from hive_table;
> +------+--------+
> | key | value |
> +------+--------+
> +------+--------+
> No rows selected (0.493 seconds)
> 0
> {code}
> The second statement results in two stages, the first stage is labeled with
> the first {{drop table}} statement rather than the CTAS statement.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
