Github user yaooqinn commented on the issue:
https://github.com/apache/spark/pull/18668
@vanzin
> the configuration of the execution Hive
Does this mean a hive client initialized by
[HiveUtils.newClientForExecution](https://github.com/apache/spark/blob/master/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveUtils.scala#L241)?
If true, this is ONLY used in
[HiveThiftSever2](https://github.com/apache/spark/blob/master/sql/hive-thriftserver/src/main/scala/org/apache/spark/sql/hive/thriftserver/HiveThriftServer2.scala#L88)
after SparkContext initialized.
Example:
`sbin/start-thriftserver.sh --conf
spark.hadoop.hive.server2.thrift.port=11001 --hiveconf
hive.server2.thrift.port=11000`
Spark Thrift Server will take 11001 as the port. `hive.server2.thrift.port`
firstly be parsed `11000`, but it will be re-writted to `11001`
[HiveThriftServer2.scala#L90](https://github.com/apache/spark/blob/master/sql/hive-thriftserver/src/main/scala/org/apache/spark/sql/hive/thriftserver/HiveThriftServer2.scala#L90)
after SparkSQLEnv init the sc. IMO the `spark.hadoop.xxx` properties can be
treat as special spark properties, which should have higher priority than its
original form `xxx`. In SparkSQLCliDriver we shall obey this rule too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
