-
Notifications
You must be signed in to change notification settings - Fork 28.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-28788][DOC][SQL]Document ANALYZE TABLE statement in SQL Reference #25524
Conversation
Test build #109467 has finished for PR 25524 at commit
|
@huaxingao Could you please attach a screenshot of the page ? |
**This page is under construction** | ||
### Description | ||
|
||
ANALYZE TABLE statement can be used to collect statistics about the table. The information can be used by the query optimizer to find a better plan. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Back-tick the reserved words for clarity.
plan -> query plan? maybe query execution plan?
Oh, I realize now you are just copying the Databricks documentation? https://docs.databricks.com/spark/latest/spark-sql/language-manual/analyze-table.html I don't think we can do that, or at least, will have to seek permission. @gatorsmile did we discuss this separately with the docs team at Databricks and that's the idea or was the idea to create simple, separate documentation from scratch? |
Test build #109521 has finished for PR 25524 at commit
|
Test build #109530 has finished for PR 25524 at commit
|
Test build #109959 has finished for PR 25524 at commit
|
@dilipbiswal @srowen @gatorsmile |
<dd> | ||
<ul> | ||
<li> If no analyze option is specified, <code>ANALYZE TABLE</code> collects the table's number of rows and size in bytes. </li> | ||
<li> NOSCAN |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@huaxingao will it read better if we bold this ?
LGTM |
Test build #110064 has finished for PR 25524 at commit
|
Looks good to me |
LGTM Thanks! Merged to master |
@dilipbiswal @gatorsmile @srowen Thank you all for your help! |
What changes were proposed in this pull request?
Document ANALYZE TABLE statement in SQL Reference
Why are the changes needed?
To complete SQL reference
Does this PR introduce any user-facing change?
Yes
Before:
There was no documentation for this.
After:
How was this patch tested?
Tested using jykyll build --serve