-
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-28789][DOCS][SQL] Document ALTER DATABASE command #25523
Conversation
cc @gatorsmile |
Test build #109465 has finished for PR 25523 at commit
|
@HyukjinKwon Hello... had a question. Would you know why these PRs are not getting linked to the corresponding JIRA ? |
@@ -18,5 +18,23 @@ license: | | |||
See the License for the specific language governing permissions and | |||
limitations under the License. | |||
--- | |||
### Description | |||
You can author metadata associated with a database by setting the `DBPROPERTIES`. Using this command |
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.
Remove "the" before DBPROPERTIES
here and below?
And maybe back-tick SCHEMA and DATABASE.
Test build #109512 has finished for PR 25523 at commit
|
Hey, @dilipbiswal. sorry for late response. Seems linked fine now :D. |
Test build #109882 has finished for PR 25523 at commit
|
Test build #109883 has finished for PR 25523 at commit
|
LGTM Thanks! Merged to master. |
Thank you very much @gatorsmile @srowen |
Test build #109886 has finished for PR 25523 at commit
|
Handled PR according to apache#25523 PR which is already merged. to make uniform accross all docs
to make uniform accross all docs
What changes were proposed in this pull request?
Document ALTER DATABSE statement in SQL Reference Guide.
Why are the changes needed?
Currently Spark lacks documentation on the supported SQL constructs causing
confusion among users who sometimes have to look at the code to understand the
usage. This is aimed at addressing this issue.
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