[SPARK-51765][DOCS][4.1] Document SQL Scripting Syntax #53194
Conversation
|
|
||
| ## Enablement | ||
|
|
||
| To enable SQL Scripting, set the `spark.sql.scripting.enabled` flag to `true`. |
There was a problem hiding this comment.
There are a lot of progress on SQL scripting in 4.1, and scripting GA can be a nice achievement to put in the 4.1 release notes. I think the feature is production ready now with the document committed (This feature is available in Databricks products for more than 6 months), but I'll leave the decision to the release manager @dongjoon-hyun
There was a problem hiding this comment.
In the meanwhile, let me merge this doc PR first.
|
thanks, merging to 4.1! |
Porting #53155 to `branch-4.1` and resolving merge conflicts. The only difference is a minor note in `docs/sql-ref-scripting.md` on how to enable SQL Scripting, since it's not enabled by default in Spark 4.1. ### What changes were proposed in this pull request? Adding documentation for SQL Scripting feature. ### Why are the changes needed? If it is not documented, it never happened :-) ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Documentation change, reviewed manually. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #53194 from davidm-db/scripting-docs-4.1. Lead-authored-by: Serge Rielau <serge@rielau.com> Co-authored-by: David Milicevic <david.milicevic@databricks.com> Co-authored-by: David Milicevic <163021185+davidm-db@users.noreply.github.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
|
Thank you, @davidm-db and @cloud-fan . |
|
Got it, @cloud-fan .
|
|
For the record, I'm waiting for @davidm-db 's action here, @cloud-fan . I'm not sure why he selectively re-acts on the community request. |
4 participants
Porting #53155 to
branch-4.1and resolving merge conflicts.The only difference is a minor note in
docs/sql-ref-scripting.mdon how to enable SQL Scripting, since it's not enabled by default in Spark 4.1.What changes were proposed in this pull request?
Adding documentation for SQL Scripting feature.
Why are the changes needed?
If it is not documented, it never happened :-)
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Documentation change, reviewed manually.
Was this patch authored or co-authored using generative AI tooling?
No.