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-29275][SQL][DOC] Describe special date/timestamp values in the SQL migration guide #25948
Conversation
@cloud-fan @srowen Please, take a look at this. |
Test build #111481 has finished for PR 25948 at commit
|
docs/sql-migration-guide.md
Outdated
- `now` - the date of running the current query. It has the same notion as today. | ||
For example `SELECT date 'tomorrow' - date 'yesterday';` should output `2`. Here are special timestamp values: | ||
- `epoch [zoneId]` - 1970-01-01 00:00:00+00 (Unix system time zero) | ||
- `today [zoneId]` - midnight today. |
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.
Shall we remove the .
at the end? For line 206 and 209, it might be natural. This line might be better be consistent with the following lines (213/214).
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.
I removed all dots because some items don't form complete sentences, and others must not as well for consistency .
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.
+1, LGTM except the minor comment on .
. It looks inconsistent.
Test build #111491 has finished for PR 25948 at commit
|
What changes were proposed in this pull request?
Updated the SQL migration guide regarding to recently supported special date and timestamp values, see #25716 and #25708.
Closes #25834
Why are the changes needed?
To let users know about new feature in Spark 3.0.
Does this PR introduce any user-facing change?
No