Github user srowen commented on a diff in the pull request:

    https://github.com/apache/spark/pull/15382#discussion_r82269678
  
    --- Diff: docs/sql-programming-guide.md ---
    @@ -869,50 +869,27 @@ access data stored in Hive.
     Configuration of Hive is done by placing your `hive-site.xml`, 
`core-site.xml` (for security configuration),
     and `hdfs-site.xml` (for HDFS configuration) file in `conf/`.
     
    -<div class="codetabs">
    -
    -<div data-lang="scala"  markdown="1">
    -
     When working with Hive, one must instantiate `SparkSession` with Hive 
support, including
     connectivity to a persistent Hive metastore, support for Hive serdes, and 
Hive user-defined functions.
     Users who do not have an existing Hive deployment can still enable Hive 
support. When not configured
     by the `hive-site.xml`, the context automatically creates `metastore_db` 
in the current directory and
     creates a directory configured by `spark.sql.warehouse.dir`, which 
defaults to the directory
    -`spark-warehouse` in the current directory that the spark application is 
started. Note that
    +`spark-warehouse` in the current directory that the Spark application is 
started. Note that
     the `hive.metastore.warehouse.dir` property in `hive-site.xml` is 
deprecated since Spark 2.0.0.
     Instead, use `spark.sql.warehouse.dir` to specify the default location of 
database in warehouse.
    -You may need to grant write privilege to the user who starts the spark 
application.
    +You may need to grant write privilege to the user who starts the Spark 
application.
     
    +<div class="codetabs">
    +
    +<div data-lang="scala"  markdown="1">
     {% include_example spark_hive 
scala/org/apache/spark/examples/sql/hive/SparkHiveExample.scala %}
     </div>
     
     <div data-lang="java"  markdown="1">
    -
    --- End diff --
    
    Here I am just fixing some duplication of docs that relate to this change. 
There were 3 identical stanzas


---
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

Reply via email to