Vamsi-klu opened a new pull request, #58037:
URL: https://github.com/apache/spark/pull/58037

   ### What changes were proposed in this pull request?
   Document `CREATE EXTERNAL TABLE` on the data source CREATE TABLE page.
   
   - Syntax diagram now shows `CREATE [ EXTERNAL ] TABLE`
   - New EXTERNAL parameter next to LOCATION: the table uses the given path, 
DROP TABLE keeps the files, and `CREATE EXTERNAL TABLE` for a data source table 
must include `LOCATION` or an equivalent path option. A table created with 
`LOCATION` or a path option is also external without the `EXTERNAL` keyword.
   - Parquet examples for `LOCATION` and `OPTIONS (PATH ...)`
   
   `CREATE EXTERNAL TABLE ... USING ... LOCATION` has been legal since 
SPARK-33651. The Hive CREATE TABLE page already documents EXTERNAL. This page 
did not.
   
   ### Why are the changes needed?
   The syntax has been supported since Spark 3.2.0, but 
`docs/sql-ref-syntax-ddl-create-table-datasource.md` still starts with `CREATE 
TABLE [ IF NOT EXISTS ]` and never shows an external example. Readers of this 
page would think EXTERNAL is Hive-only.
   
   ### Does this PR introduce _any_ user-facing change?
   No.
   
   ### How was this patch tested?
   Docs only. No unit tests for this markdown. I did not run `SKIP_API=1 bundle 
exec jekyll build` here because Bundler was not available. Please check the 
rendered page for the syntax diagram, the EXTERNAL bullet next to LOCATION, and 
that the examples use `USING parquet`, not Hive `STORED AS` clauses.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   Generated-by: Cursor Grok 4.6
   
   Made with [Cursor](https://cursor.com)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to