[SPARK-28796][DOC]Document DROP DATABASE statement in SQL Reference #25554
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
@sandeep-katta Hey, could you please update this by following the convention of existing merged PRS. |
sandeep-katta
force-pushed
the
dropDbDoc
branch
from
82de463 to
36e0a3d
Compare
Contributor
|
LGTM |
Member
|
ok to test |
|
Test build #110520 has finished for PR 25554 at commit
|
Contributor
|
@gatorsmile Thanks a lot. |
PavithraRamachandran
pushed a commit
to PavithraRamachandran/spark
that referenced
this pull request
Sep 15, 2019
### What changes were proposed in this pull request? Document DROP DATABASE statement in SQL Reference ### Why are the changes needed? Currently from spark there is no complete sql guide is present, so it is better to document all the sql commands, this jira is sub part of this task. ### Does this PR introduce any user-facing change? Yes, Before there was no documentation about drop database syntax After Fix   ### How was this patch tested? tested with jenkyll build Closes apache#25554 from sandeep-katta/dropDbDoc. Authored-by: sandeep katta <[email protected]> Signed-off-by: Xiao Li <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Document DROP DATABASE statement in SQL Reference
Why are the changes needed?
Currently from spark there is no complete sql guide is present, so it is better to document all the sql commands, this jira is sub part of this task.
Does this PR introduce any user-facing change?
Yes, Before there was no documentation about drop database syntax
After Fix
How was this patch tested?
tested with jenkyll build